The updated Workflow Builder engine (V2) brings a more structured and intelligent way to design your print production workflows. By improving how context, batching, and automation work, it reduces manual setup and helps you move faster with fewer errors. This article explains the core improvements in Workflow Builder V2, how to use them, and what changes to expect.
Smarter Context Management
Workflow Builder V2 introduces explicit context awareness for each activity. Whether you're working with OrderItem, Imposition Templates, or JobTicket, every activity clearly states the context it operates on. This clarity leads to:
Fewer configuration mistakes
A cleaner, more focused user interface
Enhanced automation and logic consistency
When configuring an activity like Send to SFTP, you can switch contexts via the dropdown menu. For example, if that activity needs access to imposition data, just select the appropriate context from the menu.
No More Loops or Special Syntax
Manual expressions like *, $., or looping are no longer necessary. V2 handles context application automatically:
Define the rule once — it runs per
OrderItemNo need to manually loop over lists
Applies consistently across activities like file transfers or preflighting
This results in simpler workflows that are easier to build and less error-prone.
Flexible Batching and Cross-Context Data Access
Batching has been reimagined for clarity and control. When you define a Batch Activity, you can set a Batch By field (e.g., ClientID, CoatingType, ColorType). These values are:
Automatically propagated downstream
Available in activities like Send to SFTP to help build filenames and logic
Each activity still works in its own context, but shared fields from batching are accessible wherever needed.
Practical Example
Batch Activity Setup
Choose to batch by:CoatingType,ColorType, andClientID.Send to SFTP Configuration
Use theImposition Templatescontext to upload files and accessBatch Byvalues for naming conventions.Switching Contexts
Use the dropdown to select fromOrderItem,Imposition, orJobTicketoutputs — each with its own defined data scope.Renaming Activities
When you rename an activity, the associated context names are automatically updated to match, keeping things intuitive.
Advanced Considerations
JavaScript activities must use
returninstead of directly modifying the context. Refer to the [Workflow Builder - GCW] Using the JavaScript Activity with V2 Engine for details.PlateContextcan only accessOrderItemfields via batched metadata — not directly.All activities are treated as working on individual items, while batching is handled internally by the engine.
Migration Details
Starting June 24, 2025, Workflow Builder V2 is automatically enabled for all newly created workflows. Existing workflows remain unchanged unless updated manually.
📝 Not what you needed?
Help us improve this article, send us an email to [email protected] — please include the article title.