Workflow Templates¶
A Workflow Template is a named, ordered sequence of steps — a routing — that a Work Order or a Manufacturing Order moves through from start to finish.
Accessing Workflow Templates¶
Open the Planning sidebar and select Workflow Templates.
Creating a template¶
Click New Template and fill in:
| Field | Description |
|---|---|
| Name | Required |
| Description | Optional |
| Applies To | Work Order or Manufacturing Order — which entity type this routing is meant for |
The template list shows each template's name, description, what it applies to, and how many steps it has. Use the row's Delete action to remove a template — this is blocked if the template is still referenced by a Work Order Template's default routing, or by a routing already in progress.
Building the routing¶
Open a template and click Add Step to append a step to the sequence. Steps run in the order you add them.
| Field | Description |
|---|---|
| Name | Required — a short description of the step (e.g. "Coil Winding") |
| Step Type | See below |
| Wait Time (minutes) | Optional, defaults to 0 |
| Checklist Template ID | Optional — links a checklist template to this step |
| Eligible Line Type | Optional — restricts which type of line this step can run on |
Some step types show extra fields once selected — see the branching fields under each type below.
Step types¶
| Type | Description |
|---|---|
| Task | A normal work step. Someone marks it complete (via a Complete Step button) to move the routing on. |
| Decision | Automatically evaluates a Condition and branches, without any manual action. |
| Parallel Split | Automatically activates every step in the same Parallel Group at once, so they can be worked concurrently. |
| Parallel Join | Automatically waits until every step in its Parallel Group has finished, then continues. |
| Rework Loop | Automatically sends the routing back to an earlier step for another pass, up to a configured number of times, then continues on. |
| Generate Work Orders | Manufacturing Orders only. Automatically creates one Work Order per item on the Manufacturing Order. |
Only Task steps ever wait for someone to act on them — every other step type resolves itself the instant the routing reaches it. A routing can still show as Blocked, but only when a step genuinely can't be resolved (for example, a Decision step whose condition refers to something that no longer exists) — not simply because of its type.
Decision steps show a Condition (JSON, optional) field plus On True → Seq / On False → Seq. The condition is checked against the record the routing belongs to (a Work Order or Manufacturing Order); if it's true, the routing jumps to On True → Seq, otherwise to On False → Seq. Leaving either blank falls through to the next step in sequence instead of jumping. Leaving the condition itself blank always evaluates as true.
Parallel Split and Parallel Join steps show a Parallel Group ID field — give the split, the join, and every step that should run between them the same ID to group them together.
Rework Loop steps show a Rework Target Seq (which step number to send the routing back to) and Max Rework Iterations (how many times to allow the loop before giving up and continuing on regardless — leave blank for no limit).
Tip
A Task step can also carry its own Rework Target Seq / Max Rework Iterations, without needing a separate Rework Loop step. This is how rejecting a Job Card tied to that step automatically sends the routing back for another pass — see Job Cards for details.
Each step in the list shows its position, name, type, branching details (where relevant), and linked checklist (if any). Use the row's Delete action to remove a step — this is blocked once a routing has actually run against it.
Variant Routing Map¶
If your organisation uses variant attributes on Manufacturing Order items (e.g. voltage class, cooling type), the Variant Routing Map card lets you tell Enture which routing to suggest for a given attribute value — for example, mapping "Voltage Class = 11kV" to an "11kV Assembly Routing" template.
Click New Mapping and choose:
| Field | Description |
|---|---|
| Variant Attribute | Required — the attribute to match on |
| Value | Required — the exact value that should trigger this mapping |
| Routing | Required — the Workflow Template to suggest when that value is set |
When an item on a Manufacturing Order has a matching variant value, its Routing picker (on the Manufacturing Order's detail page) pre-fills with the mapped routing, marked Suggested — this is only ever a suggestion, and can always be changed manually before saving. Use the row's Delete action to remove a mapping.