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 |
| Job Card Form | Optional — pick the form shown on the job card itself, filled once for the whole step. Chosen from your existing checklist templates |
| Eligible Line Type | Optional — restricts which type of line this step can run on |
| Job Card Generation | Optional — see Job card generation below |
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), linked checklist (if any), and whether it generates a job card.
Use the row's Edit action to change a step — its name, type, wait time, checklist template, eligible line type, condition, branching fields and job card settings are all editable in place. Changing a step's type clears the branching fields that no longer apply to it.
Use Delete to remove a step — this is blocked once a routing has actually run against it, which is the main reason editing exists: a step in use can't be removed and re-added.
Step position isn't editable
A step's position comes from the order steps were added. It isn't changed here, because other steps may point at it by position — a Decision's On True / On False targets, or a Rework Loop's target — and renumbering would silently send those to the wrong step.
Job card generation¶
A step can raise a Job Card automatically the moment a Work Order's routing reaches it, so nobody has to remember to create one. Set this up in the Job Card Generation section of the Add Step form, or on an existing step with the row's Job Card Generation action.
| Field | Description |
|---|---|
| Generate a job card when this step starts | Off by default. Only available on Task steps — every other type resolves itself instantly, so there would be nobody to do the work |
| Maker Group | Required once generation is on — the group who fill the card in |
| Checker Group / Approver Group | Optional — the groups who check and approve the card after it's filled. Leave either blank to skip that stage |
| Per-shift Form | Optional — a checklist template to be filled in for each shift, alongside the card's own form |
| Shift Supervisor Group (default) | Optional — who may sign off each shift's numbers. Copied onto each shift as it's filled from the roster, and changeable per shift afterwards. Leave blank to use the Maker group |
| Require sign-off on every shift | Off by default. When on, each shift's numbers must be signed off before the whole card can be submitted |
| Measure OEE Performance on this step | On by default. Turn it off for long, engineered steps where a pieces-per-minute figure means nothing — those are measured against their schedule instead |
The groups chosen here are copied onto each job card as it is created. Changing them later affects new cards only — it never rewrites who signed off on work already done. A planner can also override them on an individual card without touching the template.
Note
Changing a step's job card settings does not alter job cards already created from 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.