Versioning

See how versioning is handled in value streams.

Versioning of value streams follows a roll-forward approach. Each time a change is made, a new version of the process is automatically created. If you need to revert to an earlier version, you can do so, but this action itself generates the next version in the sequence.

When you trigger a value stream 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 value stream version, when it was modified and by whom. You can also select the previous version of the value stream and get back to it.

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