The Automation Orchestrator Client maintains a version history record for each Automation Orchestrator object. Using the version history, you can compare different Automation Orchestrator object versions and revert to a previous version.
Automation Orchestrator creates a version history record for each Automation Orchestrator object when you save the object. Subsequent changes to Automation Orchestrator objects create a new version history record. The previous versions history records are preserved and can be used to track changes to the object and revert the object to a previous version. Reverting an object to a previous version creates a new version history record.
The
Automation Orchestrator Client tracks the version history of the following
Automation Orchestrator objects:
- Workflows
- Actions
- Packages
- Policies
- Resource elements
- Configuration elements
Note: Generated workflows do not appear in the workflow version history. For example, the workflows generated by the
Generate CRUD workflows for a table workflow do not appear on the
Version History tab and cannot be pushed to any configured Git repositories. To include these workflows in the
Automation Orchestrator version history, duplicate the generated workflows.
You can access the version history of an object from the
Version History tab of the object editor page. If you are attempting to edit an object at the same time as another user, a merge conflict might occur. To resolve the merge conflict, click
Resolve to the right of the error message. On the
Resolve Conflicts window you have three options:
- Use theirs. Resolve the merge conflict by using the changes made by the other user.
- Use ours. Resolve the merge conflict by using your changes.
- Resolve. Resolve the merge conflict by editing the displayed change model. If the provided model is invalid, this option is unavailable.
