
Archiving Jobs
Original and final jobs, and in some cases even intermediate material, needs to be archived and retained for a certain period of time. SWITCH provides plenty of ways to automatically archive and organize processed jobs.
| Required tools | ||
| SWITCH | All flavors of SWITCH can implement this task. | |
| Other tools | All tools necessary for this task are built into SWITCH; no extra tools are necessary | |
| Time savings | ||
| The ROI calculation assumes this task will be used for 95% of all jobs (it assumes 5% is immediately recognized as wrong and is returned to the supplier), and that 3 minutes are saved per processed job for the different archival steps throughout the flow. | ||
More Information
SWITCH can access folders on the server it is installed on and on remote servers using the regular folder flow element. This can be used to archive jobs at any step in the workflow.
On top of that SWITCH also has an archive hierarchy flow element that is capable of storing jobs in custom subfolder structures. Those subfolder structures can merely reflect the original structure in an input hotfolder or FTP server, but they can also be modified, even with scripting.
Example Flows
The following flows present examples of how jobs can be archived in flows:
- Archiving jobs in subfolders based on the original folder structure
- Storing jobs in custom subfolders in an archive folder
- Dismantling InDesign jobs into an archive folder
- Creating custom archival folders based on the job name (PowerSWITCH only)
- Archiving jobs based on the date they were processed (PowerSWITCH only)
