Versioning
See how versioning is handled in the digital processes.
Last updated
Was this helpful?
See how versioning is handled in the digital processes.
Last updated
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.