Action blocks and checks
Updated
A block is a reusable part of a scenario: open a menu, check a connection or dismiss a popup. Call the same block from different places.
Create and call a block
- Select a connected action fragment and choose block creation from the graph context menu.
- Give it a clear name. A block call replaces the original fragment; check its continuations.
- To reuse it, add Call Block and choose the block in the Inspector.
- Connect different call parameters or enter their values. Supply the current target window when needed.
Parameters, results and completion
- External connections become parameters and results. Do not include distant nodes just to pass their data.
- The scenario continues after the block completes. Different external exits can produce separate call continuations.
- Recognition must have executed before its result is read. Passing a parameter does not trigger recognition.
- Recursive calls are unsupported and nesting is bounded. A block error or timeout stops execution.
Automatic Before/After — PRO
- Assign existing blocks before and after selected action types in the scenario Inspector. Select categories or the whole catalog.
- A node can inherit the rule, replace its assignments or disable the check.
- Checks do not recursively trigger themselves inside the called block. A Before return can skip both the protected action and its After check.
- Disabling automatic checks preserves their assignments. Explicit block calls still run; creating blocks and ordinary calls are Free.