When another user saves a newer version of the same workflow while you are editing, automation orchestrator detects the conflict when you next save, publish, or run. A dialog appears with options to resolve it.
Before you begin
- You have a workflow open in the workflow builder.
Procedure
- Save, publish, or run the workflow.
If another user saved a newer version since you opened the workflow, a conflict dialog appears. The dialog identifies who saved the newer version and which version numbers are involved.
- Choose one of the following options:
-
Save as newest version (or Publish as newest version, Run as newest version)
-
Save your changes as the next version on top of the other user's version. Automation orchestrator preserves both sets of changes in the version history. If you were publishing or running, this option also completes that action.
-
Create duplicate workflow with this version and save (or ...and publish, ...and run)
-
Create a separate workflow containing your changes. The original workflow and the other user's version are not affected. The button label reflects the action you were performing when the conflict occurred.
-
Refresh to latest
-
Discard your unsaved changes and reload the latest version from the server. Use this option when the other user's changes supersede yours.
Note:
Choosing Refresh to latest discards all unsaved changes permanently.
Results
- If you chose Save as newest version, your version appears at the top of the version history. The other user's version remains in the history.
- If you chose Create duplicate workflow with this version and save (or ...and publish, ...and run), a new workflow appears in the workflows list. Automation orchestrator names the copy
{workflow name} (Copy).
- If you chose Refresh to latest, the workflow builder displays the other user's version.