5.1 Native Workflow Templates & Approval Hierarchy

5.1 Native Workflow Templates & Approval Hierarchy

Quick Summary: Dynamics 365 Business Central provides a built-in native workflow engine that automates document approvals, record restrictions, and internal notifications without requiring external cloud integrations. Workflows operate on an Event-Condition-Response model and are initialized from standard out-of-the-box templates. The Approval User Setup table establishes the core governance structure, defining managerial chains of command via Approver IDs, monetary approval thresholds for sales and purchases, unlimited approval overrides, and substitute delegates. When an approval workflow is active, documents transition through an immutable lifecycle from Open to Pending Approval, unlocking into Released only when all criteria and limits are satisfied.

---

The Native Workflow Engine: Architecture & Execution Model

Dynamics 365 Business Central includes an integrated, database-native workflow engine designed to enforce internal controls, segregation of duties, and regulatory compliance (such as Sarbanes-Oxley or ISO quality standards). Because the engine is compiled directly into the application runtime (AL code and business logic events), it executes synchronously within the database transaction boundary. This ensures that no document or transaction can bypass approval controls due to network timeouts, latency, or external service interruptions.

The Three-Tier Workflow Anatomy

Every workflow in Business Central is modeled around three fundamental building blocks displayed on the Workflow page (Page 1501):

┌─────────────────────────┐     ┌─────────────────────────┐     ┌─────────────────────────┐
│    WHEN EVENT OCCURS    │ ──► │      ON CONDITION       │ ──► │      THEN RESPONSE      │
│  (Trigger / Entry Point)│     │  (Filter / Rule Matrix) │     │   (Action / Execution)  │
└─────────────────────────┘     └─────────────────────────┘     └─────────────────────────┘

1. When Event Occurs (Trigger): The business event that initiates the workflow step. Examples include:
   • An approval of a purchase document is requested
   • An approval of a sales document is requested
   • A customer record is changed
   • A vendor record is changed
   • A general journal batch is to be posted
2. On Condition (Filters & Thresholds): Defines the exact logical criteria that must evaluate to true for the event to execute its associated responses. Conditions apply table filters against the record being processed, such as:
   • Document Type: Order
   • Status: Open
   • Amount Including VAT: > 5000
   • Pending Approvals: 0 Conditions can also evaluate child conditions in multi-step branching workflows using hierarchical step indentation.
3. Then Response (Actions & Next Steps): One or more automated actions executed in sequence when the event occurs and the condition is met. Responses can perform operations such as:
   • Create an approval request for the record using approver type Approver and approver limit type Approver Chain.
   • Restrict record usage.
   • Send notification.
   • Show message.
   • Revert record status.

Hierarchical Step Indentation

In the Workflow Steps table, lines can be indented under parent lines. An indented line represents a subsequent event that listens only after the parent step's response completes. For instance, an approval workflow features a parent event (An approval of a purchase document is requested), followed by child events indented underneath (An approval request is approved and An approval request is rejected), each triggering its own respective response (such as releasing the document or sending a rejection notification).

---

Native Workflow Templates & Operational Coverage

Rather than building complex workflows from scratch, Business Central provides dozens of pre-configured Workflow Templates (accessed via Page 1505). Templates serve as immutable blueprints that encapsulate Microsoft's recommended business logic and best practices.

[!IMPORTANT] Templates are Read-Only: Users cannot directly edit, modify, or enable records on the Workflow Templates page. To use a template, an administrator must navigate to the Workflows page (Page 1500) and choose New -> New Workflow from Template. This action copies the template structure into an active, editable workflow record.

Core Workflow Template Categories

Master Data Record Restrictions

When a master data workflow is enabled (such as the Vendor Approval Workflow), Business Central introduces a critical operational safeguard: Record Restrictions.

• When a user creates a new vendor or modifies sensitive fields (such as bank details, payment terms, or VAT registration numbers), the workflow automatically logs a record in the Restricted Record table.
• While the record remains visible in the master list, any attempt to select that vendor on a Purchase Order or post a transaction referencing that vendor triggers a hard system validation error: "The record is restricted by a workflow."
• Only when the designated approver approves the request does Business Central execute the response Remove record restriction, permitting operational use.

---

Approval User Setup: Hierarchy, Limits & Governance

The Approval User Setup page (Page 663) forms the foundational bedrock of all document approval routing in Dynamics 365 Business Central. It defines who can request approvals, who approves for whom, and the exact financial authority each user wields.

Approval User Setup Architecture:

User ID       Approver ID   Sales Limit   Purchase Limit   Unlimited   Substitute   Admin
─────────     ───────────   ───────────   ──────────────   ─────────   ──────────   ─────
BUYER1        MGR_PURCH     $0            $0               [ ]         BUYER2       [ ]
MGR_PURCH     DIR_FIN       $10,000       $25,000          [ ]         MGR_ALT      [ ]
DIR_FIN       VP_EXEC       $50,000       $100,000         [ ]         CFO          [ ]
VP_EXEC       [BLANK]       $0            $0               [X]         CEO          [X]

Core Configuration Fields on Approval User Setup

• User ID: The Business Central login ID of the employee. Every user who submits documents or participates in an approval chain must have a dedicated record.
• Approver ID: The User ID of this user's direct supervisor or immediate approver. By linking User IDs to Approver IDs, Business Central constructs a hierarchical linked list (chain of command).
• Sales Amount Approval Limit: The maximum total monetary value (in LCY) on a sales document that this user is authorized to approve. A value of 0 means the user cannot approve any sales document.
• Purchase Amount Approval Limit: The maximum total monetary value (in LCY) on a purchase document that this user is authorized to approve.
• Request Amount Approval Limit: The maximum monetary limit for non-document requests (e.g., quotes or custom request records).
• Unlimited Sales / Purchase / Request Approval: Dedicated boolean checkboxes. Checking this flag grants the user infinite approval authority, completely bypassing numeric monetary limits. At least one executive or top-tier manager in the chain must have this flag checked to prevent approval requests from dead-ending with insufficient authority.
• Substitute: The User ID of the designated replacement approver. When an approver is out of the office, pending approval requests can be delegated to this substitute.
• E-Mail: The corporate email address used to dispatch notification alerts when approval actions occur.
• Approval Administrator: A high-level administrative privilege. A user marked as an Approval Administrator possesses system-wide authority to view all pending approval entries across all users, cancel stuck or orphaned approval requests, and delegate requests on behalf of other users.

[!WARNING] User Setup vs. Approval User Setup: Do not confuse the User Setup page (Page 119) with the Approval User Setup page (Page 663). While User Setup defines individual posting date ranges (Allow Posting From / Allow Posting To) and register time flags, Approval User Setup governs approval chains, monetary limits, and substitute delegates.

---

Approver Types & Limit Types

When configuring the response Create an approval request for the record... in a workflow, two critical parameters govern how Business Central traverses the user hierarchy:

1. Approver Type

• Approver: Traverses the standard supervisory chain defined by the Approver ID field in the Approval User Setup table.
• Salesperson/Purchaser: Routes the approval request to the specific user mapped to the Salesperson/Purchaser Code stamped on the document header.
• Workflow User Group: Bypasses the 1-to-1 manager hierarchy entirely and routes the request to a multi-member group.

2. Approver Limit Type

When Approver Type is set to Approver, the Approver Limit Type dictates how managerial thresholds are evaluated:

---

The Document Approval Lifecycle: State Machine Mechanics

Documents governed by approval workflows progress through an immutable state machine managed by the Status field on the document header:

                  ┌──────────────┐
                  │     OPEN     │ ◄────────────────────────┐
                  └──────────────┘                          │
                         │                                  │
               Send Approval Request                  Cancel / Reject
                         │                                  │
                         ▼                                  │
                  ┌──────────────┐                          │
                  │   PENDING    │ ─────────────────────────┤
                  │   APPROVAL   │                          │
                  └──────────────┘                          │
                         │                                  │
               All Approvers Approve                        │
                         │                                  │
                         ▼                                  │
                  ┌──────────────┐                          │
                  │   RELEASED   │ ──── Reopen Document ────┘
                  └──────────────┘
                         │
                    Post Document
                         │
                         ▼
                  ┌──────────────┐
                  │    POSTED    │
                  └──────────────┘

Document Status States

1. Open:
   • The initial state of a newly created sales or purchase document.
   • All fields (quantities, prices, dimensions, vendor/customer details) are freely editable.
   • Posting is strictly prohibited; clicking Post triggers a validation error stating the document must be approved and released first.
2. Pending Approval:
   • Initiated when the user selects Request Approval -> Send Approval Request.
   • The document header and line fields are locked to prevent tampering while under review.
   • One or more records are inserted into the Approval Entry table (Table 454) with Status = Open.
   • If the requester's own approval limit exceeds the document amount (and the workflow permits self-approval), the engine bypasses pending approval and immediately transitions the document to Released.
3. Released:
   • Triggered when all necessary approval entries are marked as Approved.
   • The document is unlocked for downstream warehouse operations (creating warehouse shipments, receipts, or inventory picks) and final financial posting.
   • Fields remain locked from accidental editing.
4. Reopening and Modifying Documents:
   • If a pending document requires changes, the requester can choose Request Approval -> Cancel Approval Request, reverting status to Open and canceling open approval entries.
   • If a released document requires correction before posting, an authorized user must choose Release -> Reopen. Reopening sets the status back to Open. If the document is modified, it must go through the entire approval workflow again before it can be re-released and posted.

---

Step-by-Step UI Setup Paths

1. Initializing an Approval Workflow from Template

1. Open Tell Me (Alt+Q), type Workflows, and select the Workflows list page (Page 1500).
2. On the action bar, select New -> New Workflow from Template (Page 1505 opens).
3. Expand the Purchase Documents category and select Purchase Order Approval Workflow.
4. Business Central generates a new workflow record with pre-populated event-condition-response lines.
5. In the header, review the Code and Description.

2. Configuring the Approval User Setup Matrix

1. Open Tell Me (Alt+Q), type Approval User Setup, and select Approval User Setup (Page 663).
2. Select New to create a line for each operational user:
   • Enter User ID (e.g., JDOE).
   • Select Approver ID (e.g., MSMITH).
   • Specify Purchase Amount Approval Limit (e.g., 5000) or check Unlimited Purchase Approval.
   • Select a Substitute user ID and enter the user's E-Mail.
3. Designate at least one senior finance user with the Approval Administrator checkbox enabled.

3. Modifying Conditions & Enabling the Workflow

1. On the Workflow card, locate the first line under Workflow Steps where Event is An approval of a purchase document is requested.
2. Click the link in the On Condition column to open the Event Conditions modal.
3. Adjust the filter criteria (e.g., set Amount Including VAT to > 2500 if approval is only required for orders above $2,500).
4. In the header FastTab, switch the Enabled toggle from No to Yes.

---

Common Pitfalls & Exam Gotchas

• Editing an Enabled Workflow: Attempting to modify steps, conditions, or responses on an active workflow results in the runtime error: "Enabled must be equal to 'No' in Workflow: Code=... Current value is 'Yes'." The workflow must always be disabled before editing.
• Circular Approval Chains: Configuring User A's Approver as User B, and User B's Approver as User A creates an infinite loop. When an approval request is triggered, Business Central detects the circular reference and halts with an error.
• Missing Approval Administrator: If an approver leaves the organization or takes unexpected leave without designating a substitute, their open approval requests freeze the affected documents. Without a user configured with the Approval Administrator flag, no one can cancel or delegate those requests.
• Zero vs. Blank Approval Limits: An approval limit of 0 means the user has zero approval authority (they cannot approve any document exceeding $0). Leaving a user out of the Approval User Setup table entirely causes an error when they attempt to send an approval request: "The approval user setup does not exist for User ID..."
• Self-Approval Trap: If an employee's approval limit is $10,000 and they create a purchase order for $4,500, a workflow using Approver Chain will automatically approve and release the document upon submission unless the workflow condition explicitly requires managerial review regardless of limits.