Versioning and deploying object-centric data models
This feature is currently available as a Public Preview (with a General Availability release on January 15, 2026)
Previously called Publishing and version control, these capabilities retain their core concepts and features but now come with an updated, enhanced user interface and terminology. By moving to versioning and deployment, you have more control of your content, greater content flexibility, and a clearer audit trail.
During a Public Preview, only eligible customers can access this feature. Additionally, there may be minor updates to the functionality and design of these features when they are released in General Availability.
If you would like to use this feature, create a Support ticket at Celonis Support.
For more information about our Public Preview releases, including the level of Support offered with them, see: Feature release types.
You can create and deploy numbered versions of your object-centric data models (OCDM) using built-in versioning and deployment tools. These tools let you test and deploy versions across development and production environments, giving you the option to review version histories and roll back to previous versions when needed.
The same versioning and deployment workflow is available in Studio, offering consistent benefits when creating and managing Studio packages and assets. See: Versioning and deploying (Public Preview)
An example of versioning for an OCDM within the Objects and Events area:
 |
The benefits of versioning OCDM
Creating and managing multiple versions of OCDM in the Celonis Platform provides significant benefits, particularly around governance, reliability, and iterative development. These benefits include:
Review and compare changes
Inspect and review all asset changes while in draft.
Compare versions side-by-side to view detailed changes.
Streamline version management
Create new versions with an optional, auto-generated description.
Select the specific changes you want to bundle into a single version.
Access the Version History and load any past version into a draft for inspection or hot fixes.
Efficiently deploy versions
Deploy versions with a comparison to what is currently active.
View the Deployment History, track their status, and re-deploy if needed.
You can create an OCDM version from within the Objects & Events area, generating a timestamped snapshot of its assets. Versions can then be deployed to target environments, loaded into draft, and compared with other versions.
Creating a version takes a snapshot of the assets and doesn't deploy the changes to a data pool yet. This is done via a separate deploy step, with further details provided here: Deploying an OCDM version to development or production.
For the video overview of these features:
To create an OCDM version from your dashboard:
Click Create version, opening the versioning window.
The indicator shows the number of updated assets since the last version was created.
Configure your version using the following features:
Include / exclude assets: Manually select and deselect asset changes to include in this version, with plain text search and configurable filters available for more complex packages.
Version number format: Enter a version number, an internal reference for the OCDM. We recommend using the format: MAJOR.MINOR.PATCH (e.g 1.0.0). See: .
Summary of changes: Add a summary of changes for the version for future reference, including an auto-generated summary option if required. Best practice is to add a meaningful description. This helps your team understand what's included in this version without having to look at every single asset.
Open deployment after creating the version: If selected, the deployment step opens after the version is created.
Click Create Version.
The OCDM version is created and available in the Package History area:
Optional: If you have selected to open deployment after creating this version, continue to the steps provided in Deploying an OCDM version to development or production.
OCDM version status
When creating, editing, or viewing OCDM versions, the following status are available:
Draft: This data model is currently being edited and the changes made are not yet visible to end-users. OCDM are considered as draft before they are first deployed and also when subsequently creating a new version of a deployed OCDM.
Version: This is a numbered and timestamped copy of the OCDM at the time it was created. Versions can be viewed, edited into new versions, compared to other versions, and then deployed.
Deployed version: This is a version of the OCDM that has been deployed to a production data pool, making it usable in other areas of the Celonis Platform.
OCDM version number format
For the version number format, we recommend using: MAJOR.MINOR.PATCH (e.g 1.0.0)
Major: A breaking change in the OCDM.
Minor: Tweaks in the objects and events that won’t that won't change the overall set up of the OCDM. Examples include editing an object and adding a custom event.
Patch: Very small changes, such as bug fixes, that may go unnoticed to your end-users. Examples include an update to the calculation of an event or changes in titles.
For example: 4.3.5 would be the fourth major version, the third minor release of that version, and the fifth patch of that release.
After creating an OCDM version, you can begin deploying to both the development and production environments.
Development: Deploying to development adds data jobs labeled
test:ocpm-data-jobto your data pool. These jobs can then be executed to transform data for testing purposes.Production: Deploying to production adds data jobs labeled
ocpm-data-jobto your data pool. These jobs can then be executed to transform data for productive use.
 |
For the video overview of these features:
You can start the data model deployment process in three ways:
Choose from one of the following options:
As part of the versioning workflow: When creating a version, you can select Open deployment after creating the version. This opens the deployment window after the version is created.
From the Objects & Events top bar: While viewing any page, click Deploy:
From the Package History area: When viewing any page, click Package History and then Options - Deploy version on the package version you want to deploy:
With the deployment window option, select from:
Version to deploy: Choose the numbered version to deploy.
Target: Choose from development and production environments.
Click Deploy.
The deployment process starts, with the status displayed in a pop-up.
Once successfully deployed, click Go to Data Pool to see the latest version.
OCDM version and Celonis Processes version
In the example screenshot, you'll see two version numbers. These versions are independent of each other:
OCDM version: This is version 1.0.1 of the OCDM, with the releases managed by you.
Celonis Processes version: This is version 2.0.5 of the Celonis Processes that you've installed, with the releases managed centrally by Celonis.
You can manage existing OCDM versions and deployments by clicking Package History:
In the Package History area, you then have the following management options:
Versions: Each OCDM version has the following options:
Deploy version: Make this version available in the respective environment in the data pool. See: Deploying an OCDM version to development or production.
Compare version: Run a 1:1 comparison between available versions of this OCDM, showing you the differences between them.
Load version: Open a draft version of this OCDM, giving you the ability to make changes from the timestamped version you've selected.
Deployments: Each deployed OCDM version has the following options:
Re-deploy version: Choose a previously deployed version of the package to re-deploy to production. This feature is useful when you have incorrectly deployed a version or want to fall back to a previous one.
Open deployed version in Development / Production: Click Go to deployed target to open the deployed version of this OCDM.
