Relabeling events in the Knowledge Model
Relabel events in your Knowledge Model (KM) to differentiate a central change event using its specific attributes. This ensures your data transformation logic remains scalable without requiring manual SQL duplication for multiple change types.
For more information about object-centric event logs, see: Event logs (object-centric).
To relabel events in the Knowledge Model (KM):
Click Studio and then open the package containing the KM you want to create the event log in.
Select the KM asset and then click Event Logs.
Click Create Event Log, add a display name, and optionally a description.
The system automatically generates an ID based on the display name for use in PQL statements. This ID can be manually changed if needed.
Select the lead object for the event log. The dropdown displays the objects available in your perspective.
Select the events that are relevant for the process you are tracing. The dropdown lists all the events in your perspective.
To configure dynamic events by adding attributes of event types:
Click the three dots by the name of an event type, and select Relabel event.
Click Add attribute, and select an attribute from the list. The preview updates immediately to include the new attribute in the Activity Details column. You can select any number of attributes for any number of events in the event log.
Tip
Prone to Errors: Selecting numerical attributes can generate a high volume of unique event variations, which may impact data model loading performance.
Drag and drop attributes to arrange them. Celonis concatenates the attributes in your specified order.
When you've added all the attributes you want to, select Back.
Choose your event log table settings, including:
Activity column: Select which is the activity column to visualize in the Process Explorer. By default, 'Activity' is selected.
Sorting column (optional): Events with identical timestamps will be sorted according to the values in the selected column.
While specifying a sorting column is optional, we recommend it if your data set includes activities that may have the same timestamp. If two activities belong to the same case and have the same timestamp without any configured sorting, the resulting process graph is based on implementation details (such as the alphanumerical order for
CREATE_EVENTLOG). This can result in unwanted process variants.
Verify the event log configuration using the generated table and graph previews.
The system samples your data to display these previews.
Click Save .