Automate once, stay documented forever.
Take your BPMN models straight into the workflow engine. Every revision from the engine flows back into process era automatically, so your process documentation never falls behind your automation.
Processes live in automation. The documentation goes stale.
Once a process runs in a workflow engine, it keeps evolving there: new paths, changed rules, extra steps. The process documentation usually misses all of it and within weeks shows a process that no longer exists.
The result: audits based on outdated models, risks assessed against the wrong process, and teams that no longer trust the documentation.
How the integration works
- 1
Model in process era
Business and IT model the process together in BPMN 2.0, including responsibilities.
- 2
Automate in the engine
The BPMN model is taken directly into the workflow engine and made executable there.
- 3
Sync revisions
Every new version from the engine is synced back to process era automatically.
- 4
Complete history
All revisions remain traceable in the documentation: who changed what, and when.
Supported workflow engines
process era works with BPMN 2.0 and can therefore connect to common process engines, including:
- CIB seven
- Operaton
- Mr.Know
- Scheer PAS
- and other BPMN 2.0 engines
Each tool does what it does best
In process era
- Process documentation, always in sync with the engine
- Track risks, opportunities and measures on the process
- Approvals, owners and governance
- Version history for audits and certifications
In the workflow engine
- Execution and automation of processes
- Integration with business systems and interfaces
- Monitoring of running instances
- Further development by the automation team
Why teams connect documentation and automation
No double maintenance
Changes are made once in the engine and land in the documentation automatically.
Audit-ready
Every revision is versioned and traceable, even years later.
Risks on the real process
Risks and measures always refer to the process that actually runs.
Frequently asked questions about the workflow engine integration
Which workflow engines are supported?
process era connects to BPMN 2.0 based engines such as CIB seven, Operaton, Mr.Know and Scheer PAS. Other vendors with BPMN 2.0 support are possible too. Talk to us about your engine.
Do I have to maintain processes twice?
No. The process is modelled once in BPMN and automated in the engine. New revisions from the engine are synced to process era automatically.
What happens to older versions?
All revisions are kept in the version history, so you can always see which version was live at which point in time.
Why manage risks in process era rather than in the engine?
The workflow engine is built for execution, not governance. In process era you assess risks, opportunities and measures directly on the documented process and keep approvals and owners in view.
Automation and documentation, finally in step.
15-minute demo: see how revisions from your workflow engine land in process era automatically.