# Review and record a saved plan-step configuration action

Use the exact retained workflow source, bounded native action and original-command outcome checks.

Source: https://help.smartfact.ai/manuals/automation/plan-step-actions

Review edition: 25 October 2026

Roles: author

A saved working plan can expose a bounded product configuration action. It is a deliberate native command tied to one saved plan step and its complete retained source. It is not execution of an entire cross-product plan, a release approval or a physical operation.

## Start from a saved current plan

As Author, open Review the working plan for the exact requirement. Save the intended plan first. Under Review saved product changes, use the Review link for the relevant step. Only steps with a retained supported workflow or mapping source offer that route. A shared-definition mapping uses its separate mapping procedure in [Definition mappings](/manuals/automation/definition-mappings).

Review the product configuration action identifies the saved plan revision and exact retained source. An unresolved earlier original request holds further work. You need current Automation Author authority and the native action's own product authority; recent verification is required for the configuration-creation command. Holding Owner alone does not add either working permission.

## Read the current action before confirming it

Choose Read the current action. If the plan or product context changed, return to the working plan and refresh its source. Do not change a reference merely to make an old preparation appear current.

The deployed page distinguishes Prepare the complete evidence configuration from Confirm the approved unit and inspection link. For the OrderRun configuration path it shows the complete unit mapping that will be saved for independent review. For the linking path it shows the exact approved mapping and the inspection producer's current record disposition. A record that has not been released remains unreleased.

Read the human-readable source review and open Exact source and complete configuration when needed. Check the intended unit, mapping and inspection basis against the organisation's supplied facts. A complete mapping still needs the native product's current released inspection and verified kit evidence before despatch. Do not interpret preparation as those later checks having passed.

## Confirm one attributable configuration action

Use the offered bounded editor, review its complete proposal and choose Confirm and send this configuration action only for the intended step. The product rechecks current source and native authority. A confirmed applied outcome means that configuration action was recorded, with independent review and operational gates retained. A confirmed refusal does not imply approval or physical completion.

After the result is final, return to the working plan and native product to inspect the exact resulting record and remaining work. Do not repeatedly submit the same desired effect simply because the first result is inconvenient. Configuration creation is distinct from native candidate proof, review, activation and operational use.

## Establish an interrupted original outcome

If the answer is not confirmed, further changes remain held. Under Original requests for this plan step, use Check original request. It reads the original result and sends no new effect. Retain its command and plan-step identities when passing the question to another eligible person.

An original command can be retained but proven not yet sent. Follow the displayed instruction to inspect or cancel that original in the native workspace before preparing another action. An attempted command with an unconfirmed outcome still needs reconciliation; lack of a reply is not failure evidence.

Continue through [Native drafts](/manuals/automation/native-drafts) and [Activation and recovery](/manuals/automation/activation-and-recovery) for the owning lifecycle. Approved rules remain product-owned.