These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Business Process Modeler
- Data model
The tables behind Business Process Modeler
Business Process Modeler ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 14
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Configuration:
Organizations, People and simulation scenarios establish scope and assumption basis; source mappings records conversion rules.
Modeling:
Process models carries revisions and lifecycle state; process nodes records ordered observations.
Execution:
Operation runs, operation steps and execution attempts retain the action trace and external references.
Review:
Review decisions, evidence documents, follow up actions and state history retain decisions, proof, assignments and transitions.
Access:
Users holds account records.
Every table, by feature
- Process Models5
- Process Nodes4
- Simulation Scenarios5
- Validation and Review6
- Simulation Runs6
- Evidence and Corrections7
- Shared and settings1
- Process models
Process model revisions with their organization, owner, simulation scenario and lifecycle status.
Linked to Organizations, People, Simulation scenarios - Organizations
Operating organizations that own automation definitions and action connectors.
- People
Operators, reviewers and owners who prepare, execute and review automation work.
Linked to Organizations - Simulation scenarios
Simulation scenarios that define the arrival assumptions and effective policy basis for process models.
Linked to Organizations - State history
Immutable status transition history for each automation definition.
Linked to Process models, People
- Process nodes
Node-level observations for a process model: sequence, service work, outcome and source reference.
Linked to Process models - Process models
Process model revisions with their organization, owner, simulation scenario and lifecycle status.
Linked to Organizations, People, Simulation scenarios - Operation steps
Numbered step trace with persisted input and output references.
Linked to Operation runs - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Process models, People
- Simulation scenarios
Simulation scenarios that define the arrival assumptions and effective policy basis for process models.
Linked to Organizations - Source mappings
Reviewed source-to-target field mappings per connector definition version.
Linked to Simulation scenarios - Organizations
Operating organizations that own automation definitions and action connectors.
- Process models
Process model revisions with their organization, owner, simulation scenario and lifecycle status.
Linked to Organizations, People, Simulation scenarios - Operation runs
Workflow-maintained durable run records with frozen revision and input hash.
Linked to Process models
- Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Process models, People - Process models
Process model revisions with their organization, owner, simulation scenario and lifecycle status.
Linked to Organizations, People, Simulation scenarios - Operation runs
Workflow-maintained durable run records with frozen revision and input hash.
Linked to Process models - Operation steps
Numbered step trace with persisted input and output references.
Linked to Operation runs - Evidence documents
Source evidence documents supporting validation and execution.
Linked to Process models, People - State history
Immutable status transition history for each automation definition.
Linked to Process models, People
- Operation runs
Workflow-maintained durable run records with frozen revision and input hash.
Linked to Process models - Operation steps
Numbered step trace with persisted input and output references.
Linked to Operation runs - Execution attempts
Durable attempt ledger for each triggered operation key.
Linked to Process models - Process models
Process model revisions with their organization, owner, simulation scenario and lifecycle status.
Linked to Organizations, People, Simulation scenarios - Simulation scenarios
Simulation scenarios that define the arrival assumptions and effective policy basis for process models.
Linked to Organizations - Evidence documents
Source evidence documents supporting validation and execution.
Linked to Process models, People
- Evidence documents
Source evidence documents supporting validation and execution.
Linked to Process models, People - Follow up actions
Assigned follow-up work raised from an automation definition.
Linked to Process models, People - State history
Immutable status transition history for each automation definition.
Linked to Process models, People - Process models
Process model revisions with their organization, owner, simulation scenario and lifecycle status.
Linked to Organizations, People, Simulation scenarios - Operation runs
Workflow-maintained durable run records with frozen revision and input hash.
Linked to Process models - Operation steps
Numbered step trace with persisted input and output references.
Linked to Operation runs - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Process models, People
Keys and references
A process models record links to its Organization, Owner and Definition. Process nodes connects to its Parent model. Operation runs points to the Source model, while operation steps points to its Run. Review decisions, evidence documents, follow up actions and state history all connect to the source model. The model number and revision identify the business version; an operation key and source revision identify the execution being investigated.
Migration order
- Organizations and people. Establish owning entities and operators.
- Scenarios and mappings. Create assumption sets and reviewed field conversions.
- Models and nodes. Import current revisions before their ordered observations.
- Runs and evidence. Bring over operation history with its original source references and receipts.
- Decisions and follow-ups. Reconcile reviewer decisions, status history and assigned verification work against the imported revisions.
Set up Business Process Modeler your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.