5.2 Workflow User Groups & Notification Configuration

5.2 Workflow User Groups & Notification Configuration

Quick Summary: In complex enterprise environments, approval routing frequently requires group collaboration, parallel sign-offs, or department-level routing rather than a simple one-to-one managerial chain. Workflow User Groups satisfy this requirement by organizing approvers with explicit Sequence Numbers that dictate sequential versus simultaneous (parallel) sign-offs. In parallel with routing rules, the Notification Setup framework governs how, when, and through which channels (Email or Note) approvers and submitters receive alerts, leveraging the background Notification Dispatcher job queue for scheduled digest delivery. Approvers manage their queue via the Requests to Approve workspace, while designated Approval Administrators maintain centralized authority to delegate or cancel blocked entries.

---

Workflow User Groups Architecture & Concepts

While the Approval User Setup hierarchy accommodates standard supervisor-subordinate reporting structures, many enterprise business processes require routing approvals to specialized committees, functional teams, or cross-departmental groups.

A Workflow User Group (Page 1533) decouples approval routing from individual organizational reporting charts. Common business applications include:

• Capital Expenditure (CapEx) Committees: Large asset acquisitions requiring joint review by Operations, Finance, and Executive teams.
• Vendor Onboarding Review: Master data approval requiring sign-off from both Purchasing (verifying terms) and Accounts Payable (verifying banking and tax details).
• Credit Limit Adjustments: Sales orders exceeding customer credit thresholds requiring sign-off from the Credit Risk department rather than the sales representative's sales manager.

Workflow User Group Structure:

Workflow User Group Code: CAPEX_APPROVAL
Description: Capital Expenditure Multi-Tier Approval
┌─────────────────────────────────────────────────────────┐
│ Workflow User Group Members Subpage                     │
├────────────────────┬───────────────┬────────────────────┤
│ User Name          │ Sequence No.  │ Routing Execution  │
├────────────────────┼───────────────┼────────────────────┤
│ OPS_MGR            │ 1             │ Stage 1 (Initial)  │
│ FIN_DIR            │ 2             │ Stage 2 (Parallel) │
│ LEGAL_CNSL         │ 2             │ Stage 2 (Parallel) │
│ CFO                │ 3             │ Stage 3 (Final)    │
└────────────────────┴───────────────┴────────────────────┘

To configure a workflow to use a user group, the workflow response Create an approval request for the record... is configured with:

• Approver Type: Workflow User Group
• Workflow User Group Code: Selects the designated group (e.g., CAPEX_APPROVAL).

---

Sequence Number Mechanics: Sequential vs. Simultaneous Routing

The Sequence No. assigned to each member on the Workflow User Group Members subpage dictates the precise operational order of approval requests:

1. Sequential Approval Routing (Tiered Progression)

When group members are assigned incrementing sequence numbers (e.g., Member A = 1, Member B = 2, Member C = 3), Business Central executes a phased, multi-tier approval:

• Initial Submission: Upon request submission, Business Central creates an Approval Entry for Member A with Status = Open. Simultaneously, approval entries for Member B and Member C are generated with Status = Created (staged/dormant).
• Progression: Member B receives no notifications and cannot approve the document while their entry is in Created status.
• Tier Advancement: When Member A approves, their entry transitions to Approved. Business Central immediately updates Member B's entry from Created to Open and dispatches notifications.
• Final Release: Only when Member C (the highest sequence number) grants approval does the workflow execute the Release the document response.

2. Simultaneous (Parallel) Approval Routing (Concurrent Review)

When multiple members share the identical Sequence No. (e.g., both Member A and Member B have Sequence No. = 1), Business Central routes requests concurrently:

• Concurrent Dispatch: Upon submission, the engine creates approval entries with Status = Open for both members simultaneously. Both users receive notifications and see the document in their approval queues at the same time.
• Consensus Requirement: By default, in native Business Central workflows, all members sharing that sequence number must grant approval. If Member A approves, the document remains in Pending Approval until Member B also approves.
• First-Responder Logic: Workflows can alternatively be customized to execute first-responder logic, where approval from any single user in the parallel tier completes the stage and automatically cancels the remaining peer entries.

3. Hybrid Routing Example

As shown in the CapEx diagram above, an organization can combine both patterns:

1. Sequence 1: Operations Manager reviews and approves first.
2. Sequence 2: Finance Director and Legal Counsel review in parallel.
3. Sequence 3: CFO performs the final sign-off once both Sequence 2 approvals are secured.

---

Notification System Architecture & User Setup

The Business Central notification system ensures approvers are promptly informed of pending actions, and requesters are notified when their documents are approved, rejected, or overdue.

Administrators configure notifications on the Notification Setup page (Page 1512), which can be established at the system-wide default level or tailored individually per user.

Email vs. Note Notification Methods

                                  ┌────────────────────────┐
                                  │ Workflow Event Occurs  │
                                  └───────────┬────────────┘
                                              │
                                              ▼
                                  ┌────────────────────────┐
                                  │   Notification Entry   │
                                  │      (Table 1511)      │
                                  └───────────┬────────────┘
                                              │
                        ┌─────────────────────┴─────────────────────┐
                        ▼                                           ▼
             [Notification Method: Email]                 [Notification Method: Note]
                        │                                           │
         ┌──────────────┴──────────────┐                            ▼
         │  Notification Schedule?     │                 ┌───────────────────────┐
         ├──────────────┬──────────────┤                 │ Written to System     │
         │ Instantly    │ Periodic     │                 │ Notifications & Notes │
         ▼              ▼              │                 │ (Web Client Bell Icon)│
    Immediate      Queued for          │                 └───────────────────────┘
    Email Send     Job Queue           │
                   (Codeunit 1509)     │
                        │              │
                        ▼              │
                   Batched Digest      │
                   Email Delivery ─────┘

---

Notification Dispatch Engine & Background Processing

Understanding the background dispatch architecture is essential for troubleshooting broken notification flows on the MB-800 exam:

1. Notification Creation: When a workflow executes the Send notification response, Business Central writes a pending record to the Notification Entry table (Table 1511). This record captures the recipient User ID, document record ID, notification type, and creation timestamp.
2. Instant Delivery: If the recipient's Notification Setup is set to Instantly, the system triggers immediate email generation through the tenant's configured email accounts.
3. Scheduled Batch Delivery: If the schedule is Daily, Weekly, or Monthly, the records remain staged in the Notification Entry table.
4. The Notification Dispatcher Job Queue:
   • Business Central relies on Job Queue Entry running Codeunit 1509 (Notification Dispatcher) to process staged notifications.
   • When the job queue fires, it scans Table 1511, identifies all pending entries for users with periodic schedules whose scheduled time has elapsed, bundles them into a single formatted HTML digest, and dispatches one summary email per user.
   • Successfully transmitted entries are automatically purged from the Notification Entry table to prevent duplicate delivery.

[!TIP] Email Accounts Prerequisite: Notification emails cannot be dispatched until an active email account is configured via the Email Accounts page (Page 8885). If emails are not arriving, consultants should inspect the Email Outbox (Page 8882) for failed transmissions and the Sent Emails list (Page 8884) to verify delivery logs.

---

Managing Approval Requests: The Approver & Administrator Workspace

Approvers manage their active workload through dedicated role center workspaces and action menus.

The Requests to Approve Workspace

The primary operational interface for approvers is the Requests to Approve page (Page 654). From this list, an approver can inspect the document details and execute three core actions:

1. Approve: Authorizes the request. If sequential, advances the document to the next sequence number; if final, changes the document status to Released.
2. Reject: Rejects the request. Business Central immediately changes the document status back to Open, cancels all remaining pending or staged approval entries for that document, and dispatches a rejection notification to the requester.
3. Delegate: Reassigns the approval entry to another user.
   • The Substitute Rule: In native Business Central workflows, clicking Delegate does not present a free-form user lookup. Instead, it strictly reassigns the entry to the user defined in the Substitute field of the current approver's line in Approval User Setup. If no substitute is defined, the system throws a runtime error.

Approval Comments & The Audit Trail

• Approval Comments: Both approvers and requesters can attach structured notes via the Comments action (Page 660). This is frequently used during rejections to explain why a document was rebuffed (e.g., "Vendor unit price exceeds agreed contract terms").
• The Approval Entries Log: The Approval Entries page (Page 658) stores an immutable, permanent audit log of all approval requests across the company. Each entry records:
  • Document Type and Document No.
  • Sender ID and Approver ID
  • Status (Created, Open, Canceled, Rejected, Approved)
  • Due Date
  • Date-Time Sent for Approval and Last Date-Time Modified
  • Amount (LCY)

Administrative Overrule Capabilities

If an approver is terminated, unavailable, or locked out, documents can become frozen in Pending Approval status. A user designated as the Approval Administrator on Approval User Setup has exclusive system-wide authority to:

• Open the global Approval Entries page (Page 658).
• View all pending approval entries across all departments.
• Select any entry and execute Cancel Approval Request to return the document to Open status.
• Select any entry and execute Delegate to force reassignment to the substitute.

---

Native Business Central Workflows vs. Power Automate Cloud Flows

A core functional competency evaluated in the MB-800 certification is knowing when to implement native Business Central workflows versus when to deploy Microsoft Power Automate cloud flows.

Decision Framework: When to Use Which Tool

• Deploy Native Workflows when: The approval process is strictly internal to Business Central; approvals are based purely on document amounts, purchasing limits, or standard managerial chains; zero-latency status locking is required; and the customer wants to avoid external cloud dependencies or supplementary licensing.
• Deploy Power Automate when: Stakeholders demand mobile approvals directly inside Microsoft Teams or Outlook without opening Business Central; approvals require cross-system data updates (e.g., updating a project in Jira or logging an asset in ServiceNow); or approval routing involves complex algorithms beyond standard manager limits.

---

Step-by-Step UI Setup Paths

1. Creating a Workflow User Group

1. Open Tell Me (Alt+Q), type Workflow User Groups, and select Page 1533.
2. Select New and enter a unique Code (e.g., FINANCE_REV) and Description.
3. In the Workflow User Group Members subpage, add members:
   • Line 1: User Name = CONTROLLER, Sequence No. = 1.
   • Line 2: User Name = COMPLIANCE, Sequence No. = 1 (runs parallel with Controller).
   • Line 3: User Name = CFO, Sequence No. = 2 (runs after Sequence 1 approves).

2. Linking a Workflow User Group to a Workflow

1. Open Tell Me (Alt+Q), type Workflows, and open the desired workflow (ensure it is disabled).
2. Locate the response step: Create an approval request for the record...
3. Click the blue link in the Then Response column to open the Workflow Response Options.
4. Set Approver Type to Workflow User Group.
5. In the Workflow User Group Code field, select FINANCE_REV.
6. Enable the workflow.

3. Configuring User Notification Schedules

1. Open Tell Me (Alt+Q), type Notification Setup, and select Page 1512.
2. Filter or select the target user.
3. For the line where Notification Type = Approval:
   • Set Notification Method to Email.
   • Set Schedule to Daily (or Instantly).
4. If Daily or Weekly is selected, click Notification Schedule on the action bar to specify the exact time of day (e.g., 08:00 AM).
5. Open Tell Me, type Job Queue Entries, and verify that an entry for Codeunit 1509 (Notification Dispatcher) is present with status Ready.

---

Common Pitfalls & Exam Gotchas

• The Missing Substitute Failure: When an approver clicks Delegate in Requests to Approve, Business Central does not allow selecting a user on the fly. If that approver has no Substitute configured in Approval User Setup, the delegation fails immediately with an error.
• Dormant Periodic Notifications: If an administrator configures users with a Daily or Weekly notification schedule but forgets to ensure that Job Queue Entry Codeunit 1509 (Notification Dispatcher) is running, notification records accumulate in Table 1511 indefinitely, and no emails are ever dispatched.
• Workflow User Group Sequence Gaps: Sequence numbers determine order, not strict numbering. Using sequence increments like 10, 20, 30 is a functional best practice that allows consultants to insert future approval tiers without renumbering existing members.
• Requester Cancellation Restrictions: A standard user can only cancel approval requests for documents they originated. If a requester goes on vacation with an order locked in Pending Approval, only a designated Approval Administrator can cancel the request from the Approval Entries page.