This article explains how to use the Paths Activity in your workflow to intelligently route orders based on machine availability and specific order information (context). This feature allows for flexibility in production, enabling operators to move plates between compatible machines when necessary.
Understanding Path Routing Strategies
When you add a Paths Activity to your workflow, the first step is to choose the routing strategy:
Context-Based Routing: The path is chosen solely based on information contained within the order's context (e.g., product type, size, or customer data).
Machine Availability: The path is chosen based on the real-time online/offline status of a specified machine. This is the strategy required to enable plate movement between printers by the operator.
Setting Up Machine Availability Routing
To route based on machine status, follow these steps:
Select Routing Strategy: Choose Machine Availability in the Paths Activity configuration.
Define a Machine for the Path: For the first path, select the machine that the job should prioritize (e.g., 'Indigo 7800').
Result: If this machine is online when the workflow executes, this path will be triggered.
Add a Secondary Path (Fallback): Add another path and select a different, compatible machine (e.g., 'Indigo 12000').
Result: If the primary machine ('Indigo 7800') is offline, the workflow will automatically "jump" and trigger this secondary path.
Adding Context Rules to Paths
You can make your routing even more precise by combining machine availability with context rules. This allows a path to be triggered only when both the machine is available and specific context information from the order is met.
Select Machine and Rule: Select a machine for the path (e.g., 'Indigo 7800').
Add a Context Rule: Use the Context Rule option to specify a condition, such as
Fit SRA3beingTruein the order context.Set the Logic: Ensure the condition is set as an AND condition.
Result: This path will only be triggered if the 'Indigo 7800' is online AND the
Fit SRA3value in the context is true.
Defining Activities within Each Path
It is crucial to define the complete set of necessary activities under each path you create.
Why is this important? When the Machine Availability strategy is used, it is connected with the Print Operator Console tool. This allows the operator to manually move plates from one compatible printer to another if, for example, the originally selected machine goes offline.
Required Activities: To support this flexibility, you must define all steps—such as Imposition Template and Printing Activities—under both the primary path and any secondary/fallback paths.
Tip for Configuration: To save time, fully configure the activities on your first path, then use the Duplicate Activity option and move the copied activities to the subsequent paths, adjusting any specific settings as needed.
Simulating and Testing Paths
When configuring your workflow, you need to ensure you can define the activities for every path:
Simulate Production Path (Test Only): At the bottom of the Paths Activity configuration, you will see an option to Simulate Production Path.
Change Path: Use this option to select a different path (e.g., Path B: 'Indigo 12000'). This forces the editor to focus on that path, allowing you to easily configure its specific activities.
Note: This simulation only impacts test runs within the workflow builder. For live runs, the actual online status of the machine and the context rules will determine the path taken.