
Setting Document Properties
Existing metadata and established job naming conventions can often be used to adjust workflows. This can happen in a variety of ways: metadata can be extracted from jobs and used to enforce a naming convention for all jobs, information about the jobs can be extracted from or entered into a database, etc... These tasks can be handled quite easily in PowerSWITCH through the use of scripting.
| Required tools | ||
| SWITCH | This task requires PowerSWITCH. | |
| Other tools | No additional tools are necessary for this task; however, in the return on investment calculation it is assumed that the necessary scripts will be written by a consultant. An estimated price for this work is included in the total cost of the project. |
|
| Time savings | ||
| The ROI calculation assumes this task will be used for all jobs, and that 3 minutes are saved per processed job. | ||
Example Flows
The following flows present examples for this task:
- Sort jobs in folders based on Ad Ticket Job ID (PowerSWITCH only)
- Use preflight profile depending on XMP data (PowerSWITCH only)
