# How to leave out a step when an option is selected

Use a starter rule to leave an optional block out for units whose order has one option, and include it for all others.

Source: https://help.smartfact.ai/manuals/worksteps/how-to-leave-out-a-step-when-an-option-is-selected

Review edition: 13 November 2026

Roles: author, reviewer

Sometimes a step is needed for every unit but one kind: a cleaning step that every body except aluminium needs, for instance. The starter rule **Leave out a block when an option is selected** includes an optional block for every unit except those whose order has the option you choose.

## Use the starter rule

You need the Author role, and the procedure needs a saved draft revision: a procedure you have only just created has nothing for the blanks to offer yet. The rule goes into the next draft revision. Units keep the instructions of the release they were issued with, and new units keep following the published release until a Reviewer publishes a new one.

1. Open **Procedures** and open the procedure.
2. Under **Starter rules**, find **Leave out a block when an option is selected**. It is in **Options**. You can also type a word from its title in **Search starter rules and Help**.
3. Fill in the blanks in the card's sentence, "Leave out … when … is selected.":
   - **Optional block**: one of the procedure's optional blocks.
   - **Option**: one value of one of the procedure's required options, such as Body material: aluminium. A yes-or-no option appears once, by its label: leaving the block out when it is selected includes the block when the answer is no.
4. Choose **Use this rule**. The button waits until every blank has a value.

WorkSteps saves the next draft revision with the rule in it, with the note "Began from the starter rule Leave out a block when an option is selected (version 1)". No AI is asked, and nothing is published, assigned or issued. The page then says the revision began from this starter rule and what to check next.

If **Draft definition** has changes you have not saved, the cards wait: a starter rule always starts from the saved revision. Save your changes or reload the page first.

Where SmartFACT Automation is connected to WorkSteps, you can also arrive here from **New requirement** there, which offers the cards of the procedure whose draft was saved most recently. Its **Use this rule** makes nothing: it opens that procedure's page with this card alone and its blanks filled in, and the page names the procedure. Check the procedure and the blanks, then choose **Use this rule** on the page. **See every starter rule** shows all the cards.

Where describing a condition in words is switched on for your site, the card also offers **Reword with AI**. It sends nothing: it puts the card's sentence into **Describe this condition in words** under **Slot conditions**, where you read it and choose **Propose a condition** yourself. That request counts against your limits like any other. Where describing in words is not available, the card offers **Use this rule** alone.

## What the rule does

The rule replaces the block's condition: the block's steps are included for every unit whose option has any other value, and left out where it has the value you chose. If someone later adds a value to the option, units with the new value get the block too, because it is not the value you named. A unit whose order does not give the option cannot be issued.

In the Instrument enclosure EN-400 procedure, "Leave out the material extra block when Body material: aluminium is selected" gives Clean the stainless body to every unit except aluminium ones.

## Check the examples

A starter rule saves no example, because an expected route is yours to state from the approved method: WorkSteps never works it out for you. Before you lock the revision, save examples under **Examples** that show the rule working:

- one unit whose order has the option you named, whose expected route leaves the block's steps out;
- one unit with another value of that option, whose expected route includes them.

Beside the new revision the page offers **Start an example** for each of these. It puts a unit's options in **Example JSON** and leaves the expected route empty for you to complete; then choose **Add example**. Check every option and enter the expected steps, requirements and parameters from the approved method before you save it.

Your existing examples are run again against the new revision. An example written for the old rule may now fail, and that is the point: decide whether the rule or the example is wrong before you change either.

## Publish it

Under **Review**, choose **Lock revision … and verify**, which names the revision the starter rule made. Every saved example is run, and the proof also needs each optional block both included and left out by some example. Then hand the candidate to a Reviewer. [Verify and publish a procedure](/manuals/worksteps/proof-and-publication) describes the review. A rule from a starter rule is reviewed like any other, and an author who publishes their own revision must have the Reviewer role and give a reason.

## Change it later

Nothing about a starter rule makes its rule permanent. Under **Slot conditions**, choose the block and build any other condition, or use another starter rule on the same block. Save the change as a new draft revision and publish it in the same way. Units already issued keep the instructions they were issued with.

## If the card is refused

- **This starter rule has changed since the page was opened.** WorkSteps has a newer version of the starter rule. Reload the page and fill the card in again.
- **Someone saved a newer revision.** Another author saved the draft after you opened the page. Reload it, check what they changed, then use the card again.
- **The draft already has this rule, so nothing was saved.** The card would make exactly the rule the draft has now.
