Topic Options
#18147 - 03/18/05 07:04 AM importing watch processes
stuartg Offline
OL Expert

Registered: 03/06/03
Posts: 713
Loc: Swindon, England
Watch does not correctly resolve references to printer queue output when a process is imported from another watch configuration.
When importing a process from another config, watch ought to resolve references to printer queues by either matching the names of the printers with available names in the target config; or matching names of the print queues that the printers use with those available in the target config.
It actually does neither. If a printer is available in the target config with the same uniquename, then watch imports the process and retains the uniquename, regardless of the printer name that it refers to or the queue name that it points at. If the uniquename is not available in the target config, watch removes the printer references from the imported process.
The only way to get it to behave is to manually edit the printer uniquenames in the config xml. If I do that, I may as well manually edit the xml to merge in the imported process.

#18148 - 03/22/05 01:55 PM Re: importing watch processes

When you import a process from another config file, only the imported process is examined. The important parts of the process are retained: The fact that it is a printer queue output, the name of the PTK document. Once the process is imported, all you have to do is to ensure that the PTK document was imported and to assign the correct printer in the printer output queues.

A feature request has been forwarded to the product management team.

Thank you