Version Control

The protection of automation assets from accidental changes and data loss is the main purpose of version control. It is accessed using Workbench, and tracks events in the evolution of assets along with who made them, dates, times, and so on. This hi...

To initiate changes to any automation asset in Workbench, you must first check-out the file. While working on it, the file remains locked so that concurrent changes that could render it dysfunctional are prevented. Locked files can still be view...

Changes that you make to any automation asset in Workbench creates a new version of that file. The action is triggered by the check-in process , and is always tracked in Workbench's version control system. Until you check a file in, it remains loc...

Outdated file-versions indicate modifications to the file that Workbench hasn't been synchronized to. This is common when collaborating with others on the same automation assets. Getting the latest versions of files is generally recommended before ...

The undo command is useful when you've mistakenly checked-out an automation asset or haven't made any changes to it. Instead of checking the file back in, which creates a new version with no qualitative changes, the check-out can rather be undone....

The Restore function allows you to revert any automation asset to one of its previous states. It's useful when you have unwanted changes to files, and any made between the current and restored versions can be rolled back. The restored version of t...

Note: this solution is a workaround. Using existing templates as a basis for new ones allows you to quickly transfer data models, smart parts and other DocFusion functionality. Follow the steps below to accomplish this: First, create a loca...