Process Examples
Ready-to-use BPMN and MachineSpec examples for common insurance workflows.
Table of contents
- Quick Start Examples
- Advanced Examples
- How to Use Examples
- Example Patterns
- Customization Tips
- Need More Examples?
Quick Start Examples
Simple Quote Process
A basic insurance quote lifecycle with approval workflow.
Features:
- Linear approval flow
- Guard conditions for reviewer access
- Timer-based collection expiration
- Action execution on payment
Download:
- ๐ quote-process.bpmn - BPMN diagram file
- ๐ quote-process.machine.json - MachineSpec JSON
Use Case: Basic insurance product quote and approval process.
Simple Approval Workflow
A straightforward approval process with timeout handling.
Features:
- Submit โ Review โ Approve/Reject flow
- 7-day review timeout
- Guard-protected reviewer actions
- Multiple end states
Download:
- ๐ simple-approval.bpmn - BPMN diagram file
- ๐ simple-approval.machine.json - MachineSpec JSON
Use Case: Document approval, application review, or any binary decision process.
Advanced Examples
Swimlane Process
A comprehensive process demonstrating swimlane organization across different roles.
Features:
- Customer Lane: Quote creation and document submission
- Underwriter Lane: Application review and premium calculation
- System Lane: Final policy issuance
- 30-day review deadline timer
- Multi-step approval workflow
Download:
- ๐ swimlane-process.bpmn - BPMN diagram file
- ๐ swimlane-process.machine.json - MachineSpec JSON
Use Case: Complex insurance underwriting with clear role separation.
Timer Workflow
Advanced timer handling with multiple deadlines and grace periods.
Features:
- Payment deadline: 14-day timer for initial payment
- Grace period: 7-day extension for late payments
- Multiple timer events: Cascading timeouts
- Action sequences: Payment recording, receipts, late fees
Download:
- ๐ timer-workflow.bpmn - BPMN diagram file
- ๐ timer-workflow.machine.json - MachineSpec JSON
Use Case: Payment processing with flexible deadline management.
How to Use Examples
1. Import BPMN Files
- Download the
.bpmnfile - Open the Process Editor
- Click โLoad BPMNโ in the toolbar
- Select the downloaded file
- Edit as needed for your use case
2. Import MachineSpec JSON
- Download the
.machine.jsonfile - Open the Process Editor
- Click โImport Specโ in the toolbar
- Paste the JSON content
- Click โImportโ to load the process
3. Export Your Own
After creating or modifying a process:
- Click โExport Specโ to get MachineSpec JSON
- Click โSave BPMNโ to get the BPMN file
- Save both files for version control
- Share with your team or documentation
Example Patterns
Basic Linear Flow
1
created โ [SUBMIT] โ submitted โ [APPROVE] โ approved
- Use for: Simple approval processes
- Example: Document review, basic applications
Branching Decision
1
2
review โ [APPROVE] โ approved
โ [REJECT] โ rejected
- Use for: Binary decisions with different outcomes
- Example: Credit approval, risk assessment
Timer with Fallback
1
2
waiting โ [PAY] โ paid
โ [TIMEOUT] โ expired
- Use for: Time-sensitive processes
- Example: Payment deadlines, response timeouts
Multi-Stage with Lanes
1
2
3
Customer: create โ submit
Reviewer: review โ approve
System: issue โ complete
- Use for: Cross-departmental processes
- Example: Insurance underwriting, loan processing
Customization Tips
Adapting Examples
- Change state names to match your domain
- Update event names for your business logic
- Modify timer durations for your requirements
- Add/remove lanes based on your organization
- Customize actions for your system integration
Best Practices
- Start simple: Begin with basic examples and add complexity
- Test thoroughly: Use the validation features to catch errors
- Document well: Add descriptions to your metadata
- Version control: Save both BPMN and JSON for each version
- Team review: Share examples with stakeholders for feedback
Need More Examples?
Canโt find what you need? Consider:
- Combining patterns from multiple examples
- Starting with the closest match and customizing
- Using the validation features to ensure correctness
- Checking the API Reference for advanced features
- Contributing your examples back to the project
The Process Editorโs flexibility allows you to model virtually any insurance workflow using these foundational patterns! ๐ฏ