Step Card v2

A Step card identifies one executable or control-flow unit and exposes its contract, status, and Canvas actions.

Header

The header can show:

  • Node icon and Step name.
  • Node and Method identity.
  • Rename control for ordinary Steps.
  • Expand/collapse control when the Step has Properties or nested scopes.
  • An Update indicator when a later Node definition is available.
  • The context menu.
  • Temporary Apply/Cancel controls during schema inference or Property edit mode.

Drag the header to move a Step in Pan mode. Workflow Parameters and Returns are fixed pseudo-Steps and cannot be renamed, moved, changed to another Node, or deleted.

Parameters and Returns

Parameters are values supplied to the Step. Returns describe values produced by its Node Method or control-flow contract. A Property row shows its name, type, current Value or Expression, connection state, and nested children where applicable.

Most Node templates define their Parameter and Return schemas. When a complete schema is unavailable at design time, run the Workflow through the relevant Step, then use Infer Schema to apply the discovered shape.

Context menu

The current menu can contain:

Action Behavior
Add Context parameter Adds the built-in Workflow Context Parameter when it is absent. Available only on Workflow Parameters.
Change / Reset Step Reopens Node, Method, Connection, and Template selection while preserving compatible configuration.
Update this Node Updates one outdated Step definition.
Update all <Node> Nodes Updates every outdated Step using the same Node.
Update all Nodes Updates every outdated Node definition in the Workflow.
Refresh Properties Refreshes a Sub-Workflow Step from its current child contract.
Rename Step Changes the Step name and updates supported references.
Edit Properties Opens Property structure editing. TryCatch structure is not edited through this action.
Run this step Debugs only the selected Step boundary.
Run to this Step Debugs from the Workflow start through the selected Step.
Infer from run data Reviews Property shapes derived from recent data for this Step.
Show recent logs Opens up to ten rows for this Step from the preceding seven days.
Delete Step Removes the Step and references to its name; the action is undoable.
Help for this Node Opens the matching Node help article when Node identity is available.

Unavailable actions are disabled when the pseudo-Step, edit state, Workflow identity, Node status, feature, or selected Step does not support them.

Node updates

An update merges the current Node definition with the latest available definition and preserves compatible values and connections. Review the schema-change decisions, every changed Property, and the resulting diagnostics. A version update can change behavior even when the YAML remains valid.

Review schema changes

Changing or resetting a Step, updating its Node or Method, or refreshing a Sub-Workflow can change the Parameter and Return structure. When the change needs a decision, the designer shows a schema-change tree grouped by Step and Property path. Expand an Object or Array to review changes to its children. Tick a change to apply it, or leave it unticked to keep the Step as it is where the contract permits. Node updates include these decisions in the update dialog.

Choice or control Effect
Add Adds a Property supplied by the new definition or template.
Replace Uses the proposed definition for an existing Property. Review its Value, Expression, type and children before accepting.
Remove Removes a Property that is no longer in the proposed contract.
Apply all Accepts the available proposed changes.
Keep all mine Keeps your existing configuration where the Node contract permits it.
Filter Properties Narrows the displayed tree so you can find a particular Property.
Confirm Applies the selected decisions.
Cancel Abandons the pending update.

A Property required by the Node is always added. Some required root Properties are added automatically; optional and nested changes can require a decision. Keeping your own configuration does not allow you to remove a required Node input.

For example, a new template might add a required input and propose replacing a customer-field mapping you have already configured. Accept the required input, then inspect the mapping separately before deciding whether to replace it. After confirming, review downstream Expressions and Problems, and test the Step with representative data.

See Steps, Add Step Pane, and Infer a Schema.

See also