Barcode Scanner
Steps that wait for or process input from a barcode scanner.
Overview - Steps of a Coding Scenario
Overview of all available steps and their parameters for a coding scenario.
A coding scenario is built from a sequence of steps. Each step performs one specific action or waits for a specific event before the next step begins.
Steps are divided into two categories:
- Trigger steps wait for a specific event or condition before passing control to the next step. Examples: waiting for a scan, an I/O signal, or a data import.
- Action steps execute an operation immediately and then pass control to the next step. Examples: sending a print job, syncing files, or setting an I/O signal.
Steps are executed sequentially from top to bottom. If a trigger step has not yet received its expected event, the scenario pauses at that step until the event arrives.
Steps with mandatory parameters that have not been configured are highlighted in red in the pipe. The scenario cannot be activated until all mandatory parameters are set.
I/O
Steps that wait for an I/O signal as input or control an I/O device as output.
Production Data
Steps that identify and filter master data for use in the coding scenario.
Layout
Steps that determine which label layout is used for printing and that prepare layout resources.
Send Print Job(s)
Steps that control the printing process.
Event
Trigger steps that react to changes in master data, production state changes, or the completion of system tasks.
Production
Steps that control or check the production state of the production line.
Output
Steps that write data back to the system or expose it to external systems.
FIFO Queue
Steps that manage a first-in, first-out data queue.
OPC-UA
Steps that integrate with OPC-UA compatible devices and systems.
Other
Utility steps for miscellaneous functions in a coding scenario.
Custom
Customer-specific steps available only in installations where the corresponding module is enabled.