Documents includes a Revision Control System for versioning your labels, images, and other related files. Your Revision Control System stores a history log of your files and allows you to:
Edit all revisions (versions) of your files.
Track changes made to your files.
Revert to the previous revisions.
When you edit a label file from Documents in Designer and then save it, Control Center generates a new file revision (version). Control Center keeps all previous file revisions so you can revert your label files to older versions.
To keep all file versions available, enable Versioning for your Control Center first. Go to the Administration tab > Versioning and Workflows > Document Storage Settings section.
You can also create a new file with the same name and upload it to Documents. In this case, enable Overwrite existing files checkbox. Revision number increases in this case.
By default, label files in Documents are locked for editing. You can open your label files in read-only mode. To edit your label files, you must check them out in Documents. or in Designer.
The revision control system ensures transparency when reviewing your labels, solutions, or other labeling assets in the Documents. After each document check-in, your Control Center stores information about workflow promotions, check-ins, changes, and user comments. Control Center also keeps track of who and when performed all the actions.
When checking in your files, you can choose between minor and major file versions.
Minor revisions mark smaller user edits when you work on drafts apply smaller corrections.
If you check out your document, then edit your document, then check the document in without promoting it to the next workflow step, Control Center creates a new minor version by default.
Major revisions mark significant changes in your documents made before a label or solution designer assigns files to the approvers. Typically, new major revisions correspond with workflow step promotions.
The administrator can choose which workflow step marks a change in your documents as a new major revision.
Before you can start editing your files in Documents. you have to check them out. The checked-out files are marked and locked for editing for any other user. All other users can see the current revision of the files. You can check out files in Designer or in Control Center.
To allow other users to make changes to the files, you have to check in files or discard check out status. The methods are available in the Designer and Control Center user interface.
To check out your files or folders in Control Center, right-click your selected files or folder, then select Check Outin the context menu.
To check out your files or folders in Designer, click the Check Out icon in Document Storage tab.
If you click Discard Checkout, you irreversibly lose all changes that any of the users did after checking out files. To keep the changes, check in your files or folders.
In the Info panel you can see who checked out the file, so you can ask them to save their work before you discard check out.
When you are finished editing your files and want to make them available to other users, you must check in your files or folders. You can check in files in Designer and Control Center.
To check in your files or folders in Control Center, right-click your selected files or folder, then select Check In in the context menu.
To check in your files or folders in Designer, click Check In icon in the Documents tab.
If your solutions use dynamic values (Remember the last used value option), the dynamic variables file (.dvv) must be checked out. If .dvv file is checked in, an error will occur when printing, and labels will not print.
Instead of using dynamic values, use global variables or Save Variable Data / Load Variable Data actions in your solutions.
When you check in your file, the file revision increments, and your entered comment is logged.
Every change to your files are logged in Control Center database. The file revision history includes all events occurring for files, including revisions and workflow changes.
To see all activities for the file, do the following.
Right-click your file, then click Revision History in the context menu.
You can also select your file, then go to the Revisions tab and click Full revision history.
The Revision history window with all details opens.
1. Major revision number.
2. Minor revision number.
3. Create label report. A label structure report opens in a new browser tab Label report includes meta information about your label including the graphical preview, and a list of all label objects and variables. You can also download label report as XML file.
4. Download the label file. You can download local copies of all existing label revisions from Documents to your computer. Open your downloaded copies in Designer and use them to create new revisions.
5. Compare all revisions. You can graphically compare the changes from one document revision to another.
6. Revert the current revision to the selected revision. You can revert files to any of their previous revisions. This action copies the selected file revision and adds it as the latest (current) revision.
Reverting to label revision is reserved for access roles with Read/Write permissions for the current folder. See how to set access permissions for folders in the section Managing folder permissions.
You can also preview any revision of your label file. Use this feature to avoid opening labels in Designer.
In some cases, you might want to use some older label revisions in your Automation or PowerForms solutions.
You can open and edit files depending on your Access Role. Access Roles are based on user permissions.
Requesting HEAD Revision (Latest Available)
If you request a file without specifying any revision, the latest available revision will be used in your printing solution.
If you have read/write access to the files, you can open the files with the last revision.
If you have read-only access to the file, you get:
The last revision (if the folder doesn’t have any workflow enabled).
The last approved-published revision (if the folder is assigned to the workflow process).
Requesting Specific Revision
To request a specific revision in your printing solution, provide the revision as a parameter after the file name. For example, to request revision 10 of the file
pasta.nlbl, use the syntax:
Users without permission to use older revisions will get an error message when running solutions with older revisions.
Requesting the Last Published Revision
To request a specific revision, provide it as a parameter after the file name.
To request the last published revision of file
pasta.nlbl, use the syntax:
If no file revision is approved, your solution will show the error message.