Scenario version management

Scenarios can be maintained in multiple versions allowing developers to comfortably separate different versions between three areas:

• development - one version is currently edited, version name is develop

• release - multiple released versions can be saved, with custom version tags and additional desdcription

• deployment - one version of the scenario can be picked and deployed

All the operations related to versioning are available in Scenario Editor with related buttons described in a figure below.

To switch between any of the available versions of the scenario one need to click a button at the top of the menu. It opens a window with a list of available versions including develop and deploy.

To load a version from the list you need to select it and hit Open button at the bottom right corner of the window. The loaded version is in read-only mode, which allows to investigate all details of the graph nodes without modifying them. It is also possible to validate or deploy the scenario. If you want to edit anything, it is necessary to restore the scenario to develop version, which can be achieved by pressing Restore button.

WARNING: Restore operation overrides current develop version!

All possible states and transitions between states are illustrated on the graph below.