Decisions, execution and evidence

Approval is not the end of the workflow. It is the authority to continue it.

A human decision authorizes the next action allowed by the process. It does not mean that a purchase order, posting or payment has already succeeded.

Make the decision with context

Open the assigned work item, review the request and document versions, inspect the relevant checks and confirm the authority for the action. Use the permitted approve, return, reject or other process-specific action.

Follow execution

After approval, the configured workflow continues into the next business step. Inspect its status and result. If execution is blocked or fails, use the supported recovery path; do not manufacture a second approval or duplicate business action.

A sample purchase route is request → preparation → approval → purchase order → accounting → payment → evidence. Actual actions and prerequisites depend on the selected process and Product.

What the history needs to explain

Question	Evidence
What was requested?	Business facts and document versions.
Which rule applied?	The effective process and policy revision.
Why could this person decide?	Position, assignment, authority and any valid delegation.
What was checked?	Human reviews, required checks and permitted AI output.
What did the person decide?	Decision, rationale and time.
What happened next?	The linked execution status and recorded business outcome.

Review within the right scope

Auditability does not grant every user access to every record. Company membership, role and object scope still govern who may inspect the history.

Security model · Complete a workflow