An approval flow is a set of rules that determine the approval process for a specific type of document, such as a purchase requisition. This flow can be represented as a diagram that includes approval request nodes and arcs.
- Nodes: Each node specifies an approver, which can be an individual user, a group, or an approver list. The approver receives updates on the progress of the approvable item.
- Arcs: Arcs are lines that show the order in which approval requests are processed.
This visual representation helps ensure a clear and organized approval process.
Approvers can be arranged in two ways:
Parallel: Notifies all approvers simultaneously. For example, both Gene Halas and the Purchasing Manager group receive the document at the same time.
Serial: Notifies approvers one after the other. For example, Archie Rooney and the Purchasing Agent are notified only after Gene Halas has approved the document.
For a document to be fully approved and advance through the system, all required approvers must approve it. Approvers can either approve or deny entire documents, not individual items. For example, a requisition with multiple line items must be either entirely approved or entirely denied; approvers cannot approve or deny individual line items separately.
Approval flows can contain various types of approval nodes:
Individual User: A user added to the approval flow, typically part of a supervisory chain or identified on the document being approved.
Group: Any member of the group can approve or deny the document. The first user to act completes the approval requirement, moving the request to the next node or withdrawing it if denied. Groups must be predefined via user groups.
Approval List: A combination of individual users and groups. The first user to act, whether an individual or a group member, completes the approval requirement for the entire node.