Audit
Introduction
Flowable creates a technical audit trail (history) by default. When it is required to have a business audit trail, the audit task is the easiest way to do this. For a step-by-step guide please follow the how-to.
Properties
General
Attribute | Type | Description | Category |
---|---|---|---|
Model Id | Text | Model Id identifies the element within the process model. | The model id, name and documentation properties can be found on any element. They are used respectively to uniquely identify the audit task, to give it a user-friendly name and to add a free-form description. |
Name | Text | The name of the element. This is the name displayed in the diagram. | |
Documentation | Multiline Text | The documentation attribute additionally adds a description to the component. | |
Payload | List | The content of the audit log. | The payload is optional and might contain additional information that is stored together with the audit instance. An arbitrary number of additional data can be added to the payload. |
Creator Id | Text | Creator id points to the creator who created audit log instance. If empty, default audit service creator is used. | Audit instances generated by the audit task are meant to be queries through the REST or Java API. Configuring the following identifiers will make filtering easier. Creator id: If left empty, the currently authenticated user is taken by default. An expression resolving to a user id can be set here, if the instance should be created in the context of someone else. That might make sense for example if executing asynchronously and wanting to make sure the correct user is entered. External id: this one is completely custom. |
External Id |