Operate
Review and execute a change
Follow evidence, approval, execution outcome, and history in order.
A review is not an execution
The maintenance-exception workflow is Factivum's first governed-action reference. A case joins context, source evidence, an optional scenario, a proposed change, permission and policy checks, review decisions, execution outcome, and history.
Synthetic cases demonstrate the interface and cannot perform governed commands. A server-backed case may offer commands only when current permission, policy, evidence, version, and approval checks pass. This workflow has not been production verified.
Operator sequence
- Open a case and confirm target asset, workspace, source evidence, and freshness.
- Inspect the exact before and after values in the proposed change.
- Submit for review when offered. An approval records a decision about that exact proposal; it does not execute it.
- Execute only when the case shows the required authorization and a ready action. Inspect the returned outcome and history.
If facts change
- A changed proposal or stale evidence can invalidate earlier approval. Refresh evidence and obtain a new review.
- An unknown execution outcome requires reconciliation. Do not assume success or retry blindly.
- Permission denied means the case remains readable only within your access; request the missing role instead of switching workspaces to bypass the guard.