Creating and importing events
Define events to track specific occurrences within an object-centric process. Mapping events to business objects enables the Process Intelligence Graph to calculate throughput times, identify process variants, and trigger automated alerts.
Data Engineers use events to translate raw system logs into meaningful process steps, such as mapping 'Invoice Sent' and 'Payment Received' to an 'Invoice' object. Accurate event definitions ensure that the Process Intelligence Graph correctly sequences business activities.
The platform provides three event-modeling pathways based on the source data architecture:
Modeling option | Required inputs | Primary use case |
|---|---|---|
Manual input of Event ID, data type attributes (timestamps, status), and relationships. | Use when testing isolated custom events or when source logs lack structured tables. | |
An active source table with an established data connection in a Data Pool. | Use to execute bulk event generation and auto-generate underlying SQL transformations. | |
An existing event log perspective map within Studio. | Use to differentiate dynamic change activity types from a single data stream without duplicating SQL logic. |