Order flow
Planon ProCenter enables you to define an order flow on the standard orders to enable the automatic processing of suborders in accordance with the defined process flow. The order flows must be first defined in Supporting data > Standard Orders so that they can be applied on the regular orders (by linking the standard order to them).
Order flows are very useful in performing the repetitive mini-projects effectively.
Order flows are very useful in performing the repetitive mini-projects effectively.
Workflow object
A workflow object is that through which the process flow is carried out. You can define various workflow objects on a standard order.
The following workflow objects are available:
The following workflow objects are available:
• Tasks
• Events - Start and End
• Gateways - Parallel, Exclusive, Inclusive
Task
A Task is a unit of work, a job to be performed to complete an order. A task is one of the workflow objects and is associated with a suborder in an order flow.
Event
A start/end point of an order flow.
For every order flow, there is a single start event and one or more end events depending on the order flow.
Sequence flow
Connects the various flow objects of an order flow. It links two flow objects and can have an answer condition in case it connects an exclusive/inclusive gateway to a subsequent flow object.
A flow object can be a predecessor or a successor in a sequence flow. The predecessors and successors in an order flow can be a task, an event or a gateway.
Gateway
Gateways control the process flows in an order flow. Planon ProCenter supports these gateways.
• Parallel gateway: Triggers parallel flows.
When the process arrives at the parallel gateway node, the sequence flow splits into multiple branches for each parallel task. All the outgoing tasks will then merge again into a joining parallel gateway. Only when all the tasks are completed, this gateway will be completed which then triggers the next flow object(s).
When the process arrives at the parallel gateway node, the sequence flow splits into multiple branches for each parallel task. All the outgoing tasks will then merge again into a joining parallel gateway. Only when all the tasks are completed, this gateway will be completed which then triggers the next flow object(s).
• Exclusive gateway: Allows only one of the outgoing paths to be taken in the process flow. It has only a single flow that depends on the answer on the Single select question defined on the gateway.
All other outgoing flows will be cancelled, as they are mutually exclusive. When merging, the gateway awaits for one incoming branch to complete before triggering the outgoing flow.
All other outgoing flows will be cancelled, as they are mutually exclusive. When merging, the gateway awaits for one incoming branch to complete before triggering the outgoing flow.
• Inclusive gateway: Inclusive gateway can trigger one or more outgoing paths. They could all be taken, or only one of them.
• Which outgoing flows are activated depends on the answer on the Multi select question defined on the gateway.
All other outgoing flows will be canceled.
For example, the software to be installed on a computer.
All other outgoing flows will be canceled.
For example, the software to be installed on a computer.
 | On the gateways, you can only link questionnaires having the Is audit field set to No. |