Coding Scenarios
A coding scenario defines a linear sequence of steps that are triggered by a specific input, such as an import task, a barcode scan, or a signal from an I/O device. Each step either waits for an event or performs an action, and steps can be freely arranged by dragging and dropping them in the pipe.
How coding scenarios work
A coding scenario consists of an ordered sequence of steps. Steps are executed one after another, from top to bottom.
There are two types of steps:
- Trigger steps wait for a specific event before the next step can run, for example a barcode scan, an I/O signal, or the completion of an import task.
- Action steps perform an operation immediately and then hand over to the next step, for example sending a print job or syncing files to a printer.
When a trigger step has not yet received its event, the scenario pauses at that step. As soon as the event arrives, the scenario continues from that point.
Parameters
Most steps have parameters that control their behavior. After you add a step to the pipe, click on it to open the parameter panel.
- Mandatory parameters must be set before the scenario can be activated. Steps with missing mandatory parameters are highlighted in red.
- Optional parameters allow you to refine the step behavior. If you leave an optional parameter empty, the step uses its default behavior.
For the full list of steps and their parameters, see Overview - Steps of a Coding Scenario.
Creating and configuring a coding scenario on a production line.
Overview of all available steps and their parameters for a coding scenario.