You can use version history to revert an action to a previously saved state. You can revert the action state to an earlier or a later action version. You can also compare the differences between the current state of the action and a saved version of the action.
Orchestrator creates a new version history item for each action when you increase and save the action version. Subsequent changes to the action do not change the current version item. For example, when you create action version 1.0.0 and save it, the state of the action is stored in the database. If you make any changes to the action, you can save the action state in the Orchestrator client, but you cannot apply the changes to action version 1.0.0. To store the changes in the database, you must create a subsequent action version and save it. The version history is kept in the database along with the action itself.
When you delete an action, Orchestrator marks the element as deleted in the database without deleting the version history of the element from the database. This way, you can restore deleted actions. See Restore Deleted Actions.