Configuring an activity history log
When using the Celonis Platform, all events (such as augmented attribute updates, comments, and task updates) are automatically captured and recorded against rows in a Data Model table to which they relate. You can then use the Activity history component to display these events, giving you increased visibility into your process data and strengthening your auditing options.
The Activity history component displays the following events:
Augmented attribute updates. See: Augmented attributes.
Comments. See: Comments.
Comment created
Comment deleted
Tasks
Task creation
Task action taken
Task assignee change
Task status change
Task deletion
In this example, an activity history log has been configured to show updates to an invoice (#1900000003).
 |
This activity history component could then be combined with other components, such as the related table, comments, and tasks:
 |
Prerequisites - Setting identifiers
As events are recorded against rows in a Data Model table, you must set identifiers for these tables. Identifiers allow you to identify unique records in each table, enabling you to merge the deltas to the existing and loaded Data Model.
For Data Models created from process connectors, you may find that the identifier has already been set as part of the guided configuration. You can edit or update identifiers using the same steps provided in the link below.
To learn how to set identifiers for your Data Model tables, see: Setting identifiers
 |
Configuring an activity history log
After setting identifiers for tables in your Data Model, you can now configure the activity history component within a Studio View.
Note
When creating a new app in Studio, you may have no activities recorded against the table in the Data Model. As a result, the activity history component may appear blank before you publish the app for productive use.
In View Edit Mode, drag and drop the Activity history component (one of the Object-specific details components) to your View.
Open the component settings menu and select the Data Model table you want to display the activity history for.
In this example, we are using the BKPF table:
Select the identifier mapping for each row in the table.
In this example, that includes BELNR, BUKRS, GJAHR, and MANDT:
Optional: Configure your data format and the number of activities to display per page.
Date format: This defaults to the date format used for your Celonis Platform team.
Activities per page: This is set to 5 by default.
Click Interactive Mode and test that your activity history component is working as expected.
