01
Start with stable repetition
The best first automation candidate is a frequent job with clear rules. Automating exceptions before the core path is stable usually creates more supervision rather than less.
Open knowledge base
From hotfolders to cloud nesting: levels of automation
Automation can begin with a simple hotfolder and grow into flows using XML/JDF data, branching, cloud nesting, and multiple outputs.
The vendor describes Workflow as a system of components: an input receives a job, processing steps inspect or change it, and an output routes it to a printer, cutter, folder, manual preparation, or cloud nester.
- Last checked
- 24 July 2026
- Editorial responsibility
- Prepared and reviewed by the CRINTAC team
Menu names, interface layout, and available functions can differ between PrintFactory versions, operating systems, and licence types. Check the current official source before changing production settings.
02
Cloud nesting inside the flow
Cloud nesting combines a preset, available media widths, and release criteria. Workflow sends jobs to the relevant nest queue and the completed result returns to RIP queues.
03
Measure the effect
Useful KPIs include time to production-ready output, manual touches, media utilization, routing errors, and queue waiting time.
What to remember
- Automation should follow a clear business rule.
- Cloud nesting is part of a process, not an isolated feature.
- A trial needs measurable before-and-after results.
Official vendor sources
Creating a new Workflow
Cloud Nesting — Start to Finish
Direct manufacturer sources are available to signed-in users.
Sign in through “Dashboard” in the header or request trial access.
Adapted overview based on official PrintFactory documentation. The PrintFactory name, documentation, and original materials belong to PrintFactory B.V. and their respective owners.