events in "log event in audit"

[bledii_]

Hi i'm using nuxeo 5.8 and i'm a looking at the Hr request application template ,

at various chains there are nodes of type "log event in audit" .

In this nodes there are events such as tor.request.sent and others.

Where do these events come from? How can i use/create events related to a button push on task forms (standard or custom buttons)?

[Alain_ESCAFFRE]

Hi,

First, did you know you have some documentation on the operation on this link (that gives you there a link to a tutorial that uses it). You can access this link by clickon on "See Online Help" on the operation in Studio. http://explorer.nuxeo.org/nuxeo/site/distribution/current/viewOperation/Audit.Log

This operation is designed to add event entries in the audit log. You can put what ever id you want. In this sample , we put labels id as the display is translated then, but this is not mendatory. You can try it simply first by plugging a chain using this to a button and try on a document to see the result. To plug it to workflows, you need to declare output chains on your task nodes, and from those output chains to use this operation.

[bledii_]

Hello

[bledii_]

Hello,

thank you for your answer,

yes i have read the documentation, what i am missing is the events part.

What I mean is:

In the link you sent, events are such as event= Document_Validated, whis is a "standard" nuxeo event.

In the HR request application template there seem to be some custom events used in the automation chain, that are related to the button pressed on the workflow forms.

Please check this link for an example http://tinypic.com/r/x1yljc/5 (i have uploaded a print screen)

[Alain_ESCAFFRE · Accepted solution]

You can basically put any string, there is no controlled list of events. This will be value that will be inserted in the SQL table that stores the audit entries.

And if you want't some audit entries bound to the workflow, you have to call an automatin chain that uses this operation on the output automation chain of the node. (we think of making this a parameter of the node, in the future)