You can assign a version number to a document and increment the number each time you update and reinstall the document. When you execute a document that uses a version number, the document verifies its version number against the one you specify in the trigger, and it proceeds with execution only if the two version numbers match.
You might use the version option in the following situations:
You have a single document installed on several different printers, and you must update it on all printers. If you are unable to install the updated document on all the printers, different versions of the document exist. To ensure you don’t accidentally print a job with the wrong version of the document, you include a version number in the document. When you send a trigger to the printer, in the trigger you specify the version number of the document you want to use. The document checks its version number against the one in the trigger. If it determines it is not the latest version, it prints a page reporting it is not the latest version and does not execute.
You want to install multiple versions of a document on a printer and have a means of controlling which one you execute at any given time.
To set the version number of a document:
Double-click on the Document node in the Document Structure area.
Click Conversion options and locate the version options.
Adjust the version options.
Use document versioning at printer level: Select to use version numbers with the document. Use the Document version box to enter the version number for this document.
Document version: Enter the version number of the document, or use the spin buttons to adjust the value. In a document that uses version numbers, you normally increment the version number each time you update and reinstall the document.
Install the document. You must include the version number of the document in the trigger.
To execute a document that uses version numbers:
To execute a document that uses version numbers, insert the version number of the document in the trigger, just before the “run” command. The following trigger examples all execute version 3 of the document named PAY.
|
Trigger: |
Document location: |
|
<CRTL-D> %!PS-Adobe <CR><LF> (PAY) run 3 PAY <CR><LF> |
Hard drive of a printer that has a single hard drive.
In this example, the document named PAY is loaded from the printer’s hard drive to RAM. The trigger executes version 3 of the PAY document which is stored in RAM. |
|
<CRTL-D> %!PS-Adobe <CR><LF> (Accounting\PAY) run 3 PAY <CR><LF> |
Accounting folder of a printer with a single hard drive. This example uses a relative path (a back slash does not precede Accounting). Whether you use an absolute or relative path depends on your printer configuration. For example, a printer may not have access to the root folder of its disk when it is running in PostScript mode, and would thus require a relative path. |
|
<CRTL-D>%!PS-Adobe <CR><LF> (%admin%PAY) run 3 PAY <CR><LF> |
Hard drive named “admin” of a printer. Printer may or may not have more than one hard drive. |
|
<CRTL-D>%!PS-Adobe <CR><LF> 3 PAY <CR><LF> |
Random Access Memory (RAM) of a printer. |
|
<CRTL-D>%!PS-Adobe <CR><LF> (%flash%PAY) run 3 PAY <CR><LF> |
Flash memory of a printer. |