Question

What are typical application patterns most widely in use?

Answer 1

The application patterns you meet again and again in BPM / BAW programmes, with the model shape of each:

1. Approval workflow - request task > rule-based routing (amount, risk) > one or more approval tasks (parallel or sequential, four-eyes) > fulfilment service > notification. Escalation timers on approvals.
2. Case handling / investigation - a long-running instance with a dashboard, ad-hoc activities (BAW case types or an "action menu" sub-process), documents, and milestones; BAW case management fits directly.
3. Straight-through processing with exception handling - system-only path, human task only on the error branch (question 790).
4. Onboarding / provisioning - parallel branches per system (accounts, badges, equipment) with a multi-instance or parallel gateway and a final check; compensation on cancellation.
5. Request-to-fulfil with external parties - message events for supplier / customer responses, reminders, timeouts (delayed response pattern).
6. Review cycle / iteration - draft > review > rework loop with a counter and an exit after N rounds.
7. Work distribution / queue management - one instance per item, team task lists with priorities, SLAs, reassignment rules; dashboards for supervisors.
8. Batch orchestration - a scheduler (timer start event / UCA) starts a system process that iterates over records with a multi-instance sub-process and produces a report.
9. Front-office capture - startable CSHS forms (self-service) that validate and start the back-office process; often embedded in a portal or exposed via REST to a web front end.
10. Human-in-the-loop automation - RPA / rules / AI do the work, a human task confirms exceptions or low-confidence results (the CP4BA-era pattern with ADP, ADS, RPA).

Most real processes combine two or three: an approval workflow with STP for small amounts, an onboarding with an external-party wait, a case with review cycles. Recognising the pattern early decides the modelling choices (BPD vs case, sub-process vs linked process, events vs timers) and the toolkits you need (documents, rules, messaging).

References

• BAW documentation - modeling processes and cases