Process
A Process represents a business workflow that orchestrates actors, features, and data objects to accomplish a business goal.
Key Fields
- Name: The process identifier displayed in the process landscape
- Description: Explains the workflow, purpose, and business value
- Business Products: Products that this process supports (enables filtering)
- Regions: Geographic regions where this process runs (enables filtering)
How It Works
graph LR
Process[Process] --> Elements[Process Elements]
Process --> Steps[Process Steps]
Elements --> Actor[Actors]
Elements --> Feature[Features]
Elements --> DataObject[Data Objects]
Steps --> |connects| Elements
A process contains:
- Elements: The actors, features, data objects, and timers involved
- Steps: Directed edges showing the flow of work between elements
Process Orchestration
Process steps can trigger or wait for other processes:
- Triggers Process: This step starts another process
- Awaits Process: This step waits for another process to complete
System-Independent Steps
Processes can include steps that occur outside of IT systems:
- Physical actions: Loading, unloading, driving
- Manual handovers: Document exchanges, verbal instructions
- Physical movements: Truck routes, walking paths
These steps are modeled using actors and data objects without system assignments.
Example:
story:
# Physical movement
- sourceElementId: "actor-lkw"
targetElementId: "actor-empfangsstation"
label: "fährt zu"
# Physical action
- sourceElementId: "actor-fahrer"
targetElementId: "actor-lkw"
label: "entlädt"
Learn more about Physical World Modeling →
Integration
- Storage:
korgraph database, type process
- Parent: Lives under a
processlandscape
- Export: Included in BPMN 2.0 XML exports
Tips
- Use clear, descriptive names that explain the business outcome
- Add scope (products/regions) early for better organization
- Document orchestration dependencies for complex workflows