Process Orchestrator
The intended central orchestration of an end-to-end process.
This topic describes development or product direction. It does not confirm availability in your environment.
What can you do with it?
This explains the product direction: governing process steps, systems, people and exceptions together.
- Process requirement
- Intended orchestration
- Controlled result
How to start
- Map the process
- Define actions and controls
- Describe exception handling
On this page
Process Orchestrator is in development. This section describes product direction and the intended operating model, not current screen-by-screen instructions.
La navegación y el resumen de la página están en español. El contenido técnico de esta página permanece temporalmente en inglés y se traducirá de forma gradual.
Process Orchestrator is intended to become the central start point of SAS: the place where a customer designs a flow, uses the required building blocks, follows running process instances, handles human work and exceptions, and improves outcomes.
The core promise is to move from separate process steps to a controllable chain in which requests, tasks, decisions, SLA status, systems, and data come together.
Product direction
| Area | Intended role |
|---|---|
| Design & Model | Make processes, decisions, gateways, and dependencies explicit. |
| Orchestrate & Execute | Coordinate systems, people, data, actions, and events. |
| Monitor & Control | Show instances, status, SLA, alerts, and the reason attention is required. |
| Work & Collaborate | Bring tasks, priority, deadlines, and process context to people. |
| Analyze & Improve | Use cycle time, volume, rework, automation rate, and trends to improve. |
| Govern & Assure | Apply roles, permissions, policy, security, audit, and evidence. |
The following pages explain the direction without presenting it as current product instructions.
En esta sección
Take the next step
Use the reference material for details or discuss your question with the team.
Ask your question