Chapter 12: Complex Workflow Patterns
Chapter Objectives:
Implement sequential workflow patterns for ordered processes
Configure parallel task workflows for simultaneous execution
Design conditional branch workflows for dynamic routing
Create escalation workflows with time-based reassignment
Build recurring workflows for periodic processes
Understand task precedence and dependencies
Prerequisites:
Completed basic workflow configuration (Chapters 5-7)
Understanding of status rules and release conditions
Familiarity with triggers and scenarios
Experience with at least 2-3 workflow implementations
12.1. Sequential Workflows
Pattern Description: Tasks execute one after another in fixed order.
When to Use:
Process has clear ordered steps
Each step depends on previous completion
No parallelization possible or desired
Documentation trail important
Configuration Approach:
Example: Customer Onboarding:
Workflow: Customer Onboarding (CUST-ONBOARD)
Table: Customer (18)
Trigger: New customer created
Task 1 - Verify Contact Information:
Code: VERIFY-INFO
Status: Released (starts immediately)
Assigned to: [18:29]
Best Practices:
Clear task descriptions indicating sequence
Due dates progressively later (stagger deadlines)
Each task verifies prerequisite completion
Manual override option for urgent cases
12.2. Parallel Task Workflows
Pattern Description: Multiple tasks start simultaneously, all must complete before proceeding.
When to Use:
Independent tasks can execute concurrently
Faster overall completion desired
Tasks assigned to different users/teams
No dependencies between parallel tasks
Configuration Approach:
Example: Sales Order Processing:
Workflow: Order Processing (ORD-PROCESS)
Table: Sales Header (36)
Trigger: Order released
Parallel Tasks (start simultaneously):
Task 1A - Credit Check:
Code: CREDIT-CHECK
Status: Released
Assigned to: FIN-TEAM
Due Date: +1D
Activity Type: Manual
Task 1B - Inventory Allocation:
Code: INV-ALLOC
Status: Released
Assigned to: WH-TEAM
Due Date: +1D
Activity Type: Manual
Task 1C - Shipping Schedule:
Code: SHIP-SCHED
Status: Released
Assigned to: LOG-TEAM
Due Date: +1D
Activity Type: Manual
Synchronization Task:
Task 2 - Final Review:
Code: FINAL-REVIEW
Status: Open (waits for all parallel tasks)
Assigned to: [36:29]
Synchronization Strategies:
Strategy 1: All Tasks Required:
Strategy 2: Majority Required (Manual Config):
Best Practices:
Same due dates for all parallel tasks
Clear indication of parallel execution in descriptions
Monitor for bottlenecks (one slow task delays all)
Reassign capability if team overloaded
12.3. Conditional Branch Workflows
Pattern Description: Different tasks execute based on data conditions (if-then-else logic).
When to Use:
Process varies by data values
Different approval levels for different amounts
Route to different teams based on criteria
Mutually exclusive execution paths
Configuration Approach:
Example: Credit Approval Workflow:
Workflow: Credit Limit Change (CREDIT-CHANGE)
Table: Customer (18)
Trigger: Credit limit modified
Conditional Branching:
Branch A - Low Amount (<\,000):
Task: Supervisor Approval
Code: SUPER-APPROVE
Status: Open
Assigned to: SUPERVISOR
Due Date: +2D
Activity Type: Conditional
Line 9999 (Release):
Condition: Customer."Credit Limit (LCY)" <= 10000
Condition: Customer."Credit Limit (LCY)" > 0
Branch B - Medium Amount (\,001-\,000):
Task: Manager Approval
Code: MGR-APPROVE
Status: Open
Assigned to: MANAGER
Due Date: +3D
Activity Type: Conditional
Line 9999 (Release):
Condition: Customer."Credit Limit (LCY)" > 10000
Condition: Customer."Credit Limit (LCY)" <= 50000
Branch C - High Amount (>\,
Mutually Exclusive Conditions:
Best Practices:
Document branching logic clearly
Test all branches thoroughly
Handle edge cases (what if amount = 0?)
Consider future branches (extensibility)
12.4. Escalation Workflows
Pattern Description: Tasks automatically reassign to higher authority based on time or conditions.
When to Use:
SLA enforcement critical
Overdue tasks need escalation
Management oversight required for delays
Bottleneck prevention important
Configuration Approach:
Custom Status Rule:
Field No: 11 (Assigned to)
Value: MANAGER-ID
Validation Formula (Condition):
Critical Date <= [TODAY]
Example: Auto-Escalation Workflow:
Workflow: Sales Quote Follow-up (QUOTE-FOLLOWUP)
Table: Sales Header (36)
Trigger: Quote created
Task: Follow Up Call
Code: FOLLOWUP-CALL
Status: Released
Assigned to: [36:29] (Salesperson)
Due Date: +3D
Critical Date: +2D
Activity Type: Interaction
Contact No.: [36:5052]
Template Code: PHONE CALL
Escalation Rule:
Custom Status Rule (Line 10001):
Description: "Escalate to manager if uncompleted by critical date"
Field No: 11 (Assigned to)
Value: SALES-MGR
Validation Formula:
Condition 1: Critical Date reached
Table ID: 72777606 (WorkFlow Entries)
Field No.: 9 (Critical Date)
Filter String: <=[TODAY]
Multi-Level Escalation:
Status Rule 1 (Line 10001) - First Escalation:
Field No: 11 (Assigned to)
Value: MANAGER
Condition: Critical Date <= [TODAY] AND Assigned to = SALESPERSON
Status Rule 2 (Line 10002) - Second Escalation:
Field No: 11 (Assigned to)
Value: DIRECTOR
Condition: Due Date < [TODAY]
Best Practices:
Clear escalation criteria
Notify all parties of escalation
Document escalation reason
Prevent infinite loops (check already escalated)
12.5. Recurring Workflows
Pattern Description: Workflows trigger periodically for recurring processes.
When to Use:
Annual reviews required
Monthly reconciliations
Quarterly audits
Periodic maintenance tasks
Configuration Approach:
Example: Annual Customer Review:
Workflow: Annual Customer Review (CUST-ANNUAL-REV)
Table: Customer (18)
Recurring Frequency: Annually
Trigger (Initiated By):
Condition: Last review date > 12 months ago
(Conceptual - may require custom field tracking)
Task 1 - Update Contact Information:
Code: UPDATE-INFO
Status: Released
Assigned to: [18:29]
Implementation Considerations:
Best Practices:
Track last execution date (custom field may be needed)
Handle missed periods (if system down)
Notification before review due
Flexible rescheduling if timing conflicts
12.6. Multi-Stage Approval Workflows
Pattern Description: Sequential or parallel approvals at different organizational levels.
Sequential Approvals:
Parallel Approvals:
Example: Purchase Order Approval:
Workflow: PO Approval (PO-APPROVE)
Table: Purchase Header (38)
Trigger: PO amount > \,000
Sequential Approval Workflow:
Task 1 - Department Manager Approval:
Code: DEPT-APPROVE
Status: Released
Assigned to: DEPT-MGR
Due Date: +2D
Activity Type: Conditional
Description: "Approve PO [38:3] for [38:179]"
Line 10000 (Completion):
Manual approval required
Task 2 - Finance Manager Approval:
Code: FIN-APPROVE
Status: Open
Assigned to: FIN-MGR
Due Date: +4D
Activity Type: Conditional
Line 9999 (Release):
Condition: Task DEPT-APPROVE Status = Completed
Condition: Purchase Header.Amount > 5000
Line 10000 (Completion):
Manual approval required
Task 3 - Executive Approval (if > \,
Conditional Approvals:
Different approval paths based on amount or other criteria
Amount <= \,000:
Single approval (Department Manager)
Amount > \,000 AND <= \,000:
Two approvals (Department + Finance)
Amount > \,
12.7. Task Precedence (Dependencies)
Feature: QUA Precedance table defines prerequisites between tasks.
Current Status: Table structure exists, enforcement logic status uncertain.
Configuration:
Workaround (Using Status Rules):
