LogoLogo
CommunitySupport PortalYouTubeStart a free trial
OE
  • Welcome
  • Commerce Engine
  • Orchestration Engine
  • API Documentation
  • Release Notes
  • Changelog
OE
  • Orchestration Engine
  • Getting Started
    • What is OE?
      • What are the benefits?
      • Use Cases
    • Provisioning
    • Understanding Make
    • OE Learning Trails
      • Setting up a First Digital Process
      • Adding a Conditional Step in a Digital Process
  • Management Dashboard
    • Accessing OE
    • Orchestration Center
    • Forms
    • KPIs and Analytics
    • Rulestore
    • Events
      • Event Registry
      • Event Log
      • Cloud Events in OE
      • Events Authentication and Configuration
      • Working with Event Data
    • Admin
      • Users and Roles
      • Integration with Celonis
      • Make Team
      • Task Inbox and Tasks
  • Digital Processes
    • Digital Processes Dashboard
    • Digital Processes Example
    • Working with Digital Processes
      • Digital Process Components
      • Creating a Digital Process
      • Editing a Digital Process
      • Testing a Digital Process
      • Conditional Process Runs
      • OE Make Modules
      • Configuring a Connection between OE and Make Modules
      • Setting a Trigger to Wake Up a Paused Digital Process
      • Cloning of Make Scenarios in OE Digital Processes
    • Data Flow between OE and Celonis
      • Retrieving Data from Celonis
      • Sending Data from OE to Celonis
      • Sending Form Submission Data from OE to Celonis
      • Sending Forms Magic Links Data from OE to Celonis
    • Process Context
    • Datastore
    • Versioning
    • Data Retention Policy
  • Troubleshooting
    • Firewall Allowlisting
    • Digital Processes Debugger
    • Generating a HAR File with Logs
    • FAQ
      • Receiving Alerts for Scenario Errors
      • Make Scenario Not Valid in OE
      • Digital Processes Blocked by Scenario Errors
      • Invalid Digital Processes
Powered by GitBook
LogoLogo

Resources

  • Emporix.com
  • Developer Policy
  • Terms of Use

Find us

  • LinkedIn

© 2025 Emporix. All Rights Reserved.

On this page

Was this helpful?

Export as PDF
  1. Digital Processes

Versioning

See how versioning is handled in the digital processes.

PreviousDatastoreNextData Retention Policy

Last updated 1 month ago

Was this helpful?

The versioning of digital process is based on the roll-forward approach. It means that with every change a new version of the process is created. If you want to get back to a previous version, you can do so, but it actually creates the next version of the process.

When you trigger a digital process and it starts to run, you have an instance of that process. If the process is at version 1, that instance is an instance of version 1. Supposing you have 200 running instances at version 1 and you modify your process and save it as version 2, the next instance of that process that you run is a version 2 instance. This does not change the 200 running instances at version 1.

It is possible to have many instances of many different versions all running at the same time. When a new version is created, it doesn't stop the previous ones from running.

Additionally, using the Show Versions function, you can check what is the current digital process version, when it was modified and by whom. You can also select the previous version of the digital process and get back to it.

Choosing to revert to an older version of the digital process results in changing the process to the older configuration, but with a new version number.