Schedule transformations for individual perspectives for object-centric process mining (2024-05-07)
This is a Limited Availability functionality.
Instead of running the complete OCPM data job to create objects and events for all your enabled processes, you can now set up schedules to run the transformations for one perspective at a time (or more than one if you want). This feature is currently in Limited Availability - if you'd like to try it out now, open a Service Desk ticket to request it. We're planning to have it in General Availability soon.
When you run the OCPM data job through a schedule where you've selected perspectives, we'll identify all the objects and events that are part of those perspectives. Then we’ll run only the transformations that are needed to create those objects and events from your source system data. You can create dedicated schedules for the Celonis-supplied perspectives for the Celonis catalog processes, and also for your custom perspectives. For the full instructions, see Running transformations.
Because Data Integration can only run one instance of a data job at a time, we've added an execution setting to enable queuing of data jobs. When this is enabled, if an instance of the OCPM data job (or any data job) is running and another instance of the same data job is scheduled to start, the second instance will be queued until the first finishes. If queuing of data jobs isn't enabled, the second instance would be skipped, as it would before this feature. While the feature is in Limited Availability, you'll need to enable queuing of data jobs manually for every schedule where you've selected perspectives. When the feature enters General Availability, queuing of data jobs will become the default behavior for all schedules in the OCPM Data Pool.
Queuing of data jobs is available in every data pool, not just the OCPM Data Pool. So you can activate it for other data jobs if you want to - including case-centric data jobs. In every data pool that doesn't have object-centric data models active, queuing of data jobs will be off by default. In every data pool that does (if you're using the feature that gives you object-centric data models in all your data pools), it will be on by default.