Safe tests

Use synthetic inputs only

Safe tests accept invented, non-production inputs only. Do not enter a real document, person, destination, customer value, exported record, or copied identifier. Use the displayed safe-test fields to describe a hypothetical input that matches the saved workflow selector.

The safe-test result is an authoring record, not a preview of a live document. It does not read from Capture, Accounting, Operations, or another product record.

Run a safe test

Save the workflow draft first, then choose Test workflow and complete the synthetic input. RS1 evaluates the saved revision and records the result in Safe test history. Unsaved edits are not included, and a test does not publish, activate, execute, deliver, assign, or convert anything.

Read the deterministic trace

The trace is deterministic: the same saved dependencies and the same synthetic input produce the same authoring evaluation. Its display is intentionally limited to privacy-safe selector results, step outcomes, intended actions, and confirmation that no real action occurred. It does not expose source records, personal details, raw diagnostics, internal identifiers, checksums, or directory and grant values.

Behind that display, qualifying evidence remains tied to the exact saved draft revision and checksums, referenced policy revision and checksum, directory eligibility, and active grants used for that run. Readiness verifies those dependencies even though the trace does not display their underlying values.

Understand zero side effects

A safe test records evidence only. It never changes a document, creates a destination record, starts a workflow, opens an approval, sends a notification, applies a delegation, changes a queue, or contacts a person. It has zero real side effects.

Current versus outdated evidence

Latest is the newest stored run, whether it passed or failed. Current is a qualifying successful run whose exact dependencies still match the saved authoring state. A newer failed run is Latest while an earlier qualifying success can remain Current until any dependency changes.

Saving a draft or policy change, changing the selector or template compatibility, or a change in directory eligibility or active grants makes earlier evidence outdated. Run a new safe test after resolving the change; do not treat an outdated result as readiness evidence.

Check readiness

Choose Check readiness for the saved workflow after reviewing the current safe-test evidence. Readiness checks the saved draft and its dependencies, including validation, template compatibility, policy reference, directory eligibility, active grants, and qualifying Current evidence. A ready result is limited to Phase 1 authoring readiness; it does not enable Publish or create live behavior.

Common readiness blockers

• Resolve validation issues in the saved workflow or referenced policy draft.
• Run a new safe test when no qualifying Current evidence exists or the evidence is outdated.
• Choose a compatible displayed template and destination when template compatibility is blocked.
• Ask an administrator to review the selected organization’s current directory eligibility or Workflow grant when an offered target or authority has changed.
• If Settings is absent in Preview, ask an administrator to confirm the selected organization, Workflow binding, and explicit grant. Production remains unavailable until UAT is complete.

Phase 1 boundary: Safe tests and readiness are available to authorized accounts in Preview and preserve authoring evidence only. Publish, activation, execution, approval delivery, notification delivery, delegation, and conversion are not available. Production remains disabled until UAT is complete.