Product direction · 1.0
Future components for matrices, rules, policies, expected state, and Operational Activities.
This page describes Process Orchestrator product direction. Exact functionality may change before release.
Navigation und Seitenzusammenfassung sind auf Deutsch. Der technische Inhalt dieser Seite ist vorläufig noch auf Englisch und wird schrittweise übersetzt.
The Process Orchestrator direction extends beyond workflow steps. Additional control components are intended to make decisions, policy, and recurring assurance explicit.
A matrix compares dimensions and determines an outcome. For example:
| Role | Location | Contract type | Required result |
|---|---|---|---|
| Consultant | Office | Employee | Managed laptop and standard application set |
| Manager | Restricted location | Employee | Secure laptop, MFA, and additional approval |
| External | Any | Contractor | Limited access or approved BYOD route |
The result can be linked to the reason, conditions, approval, automation, and later control.
Policy records why a result is required. Entitlements describe what a person, case, or system should receive under that policy. This makes questions such as “Why does this person have this laptop or access right?” answerable from structured context.
The expected state can be compared with the actual state reported by connected systems. A mismatch can create evidence, an exception, a human task, an automated action, or escalation.
Operational Activities are recurring or event-driven controls. Examples include checking that former employees have no active accounts, that exceptions are still valid, or that allocated assets match policy.
These are product-direction concepts. Exact configuration and runtime behavior will be documented as they become available.