Design & Model — Process Orchestrator
De beoogde inrichting van processtappen, beslissingen en afhankelijkheden.
Dit onderwerp beschrijft ontwikkeling of productrichting. De beschreven mogelijkheden zijn geen bevestiging van beschikbaarheid in jouw omgeving.
Op deze pagina
This page describes Process Orchestrator product direction. Exact functionality may change before release.
De navigatie en paginasamenvatting zijn Nederlands. De technische inhoud op deze pagina is voorlopig nog in het Engels en wordt stapsgewijs vertaald.
The modeler direction uses recognizable building blocks such as start, task, user task, decision, gateway, subprocess, end, and connector. The purpose is not to reproduce technical architecture diagrams. It is to show the process as the organization experiences it.
Intended value
- business logic becomes visible instead of being hidden in scripts;
- parallel work, decisions, and dependencies can be understood without reading code;
- reusable components and validation help keep models consistent;
- versions make controlled change possible;
- integrations become part of the flow rather than separate technical projects.
A process should be understandable by business, operations, and IT while remaining precise enough for controlled execution.