Event

Trigger steps that react to changes in master data, production state changes, or the completion of system tasks.

This tab provides trigger steps that react to changes in master data, to production state changes, or to the completion of system tasks.


On product change

This trigger step reacts when a change in the product master data is detected: a product is added, edited, or deleted in manage.ID, a change request for a product is approved in the approval system, or a product is created or updated through the Web API.

This step has no parameters.

Examples

Example 1: Stopping the Production when the Running Product Is Blocked

When a user sets the status of a product to Blocked, the On product change step triggers the scenario. The Check Database Value step checks whether the product in the current production has the status Blocked. If it does, the Stop Production step stops the production.

Example 2: Printing a Check Label after the Product Data Changes

When a user changes the master data of a product, the On product change step triggers the scenario. The Check If Production Running step verifies whether there is an active production on the line. If a production is running, the Identify layout step reads the name of the label layout from the master data, and the Send print job to printer step prints a label with the updated product data, so the operator can check it.

Limitations

  • The step triggers on a change to any product, not only the product in the line’s current production.
  • The step doesn’t say which product changed or what changed. Subsequent steps work with the line’s current production data.
  • When many products are saved at once, for example through the Web API, the scenario runs once for each product.

On order change

This trigger step reacts when a change in the production order master data is detected: a production order is added, edited, or deleted in manage.ID, a change request for a production order is approved in the approval system, or a production order is created or updated through the Web API.

This step has no parameters.

Examples

Example 1: Stopping the Production when the Running Production Order Is Cancelled

When a user sets the status of a production order to Cancelled, the On order change step triggers the scenario. The Check Database Value step checks whether the production order in the current production has the status Cancelled. If it does, the Stop Production step stops the production.

Example 2: Printing a Check Label after the Order Data Changes

When a user changes the master data of a production order, for example the batch number, the On order change step triggers the scenario. The Check If Production Running step verifies whether there is an active production on the line. If a production is running, the Identify layout step reads the name of the label layout from the master data, and the Send print job to printer step prints a label with the updated production order data, so the operator can check it.

Limitations

  • The step triggers on a change to any production order, not only the production order in the line’s current production.
  • The step doesn’t say which production order changed or what changed. Subsequent steps work with the line’s current production data.
  • When many production orders are saved at once, for example through the Web API, the scenario runs once for each production order.

On product or order change

This trigger step reacts when a change in either the product master data or the production order master data is detected: a product or production order is added, edited, or deleted in manage.ID, a change request is approved in the approval system, or a product or production order is created or updated through the Web API.

This step has no parameters.

Examples

Example 1: Stopping the Production when the Running Production Order Is Cancelled

When a user sets the status of a production order to Cancelled, the On product or order change step triggers the scenario. The Check Database Value step checks whether the production order in the current production has the status Cancelled. If it does, the Stop Production step stops the production.

Example 2: Printing a Check Label after the Product or Order Data Changes

When a user changes the master data of a product or a production order, for example the batch number, the On product or order change step triggers the scenario. The Check If Production Running step verifies whether there is an active production on the line. If a production is running, the Identify layout step reads the name of the label layout from the master data, and the Send print job to printer step prints a label with the updated data, so the operator can check it.

Limitations

  • The step triggers on a change to any product or production order, not only the ones in the line’s current production.
  • The step doesn’t say which record changed or what changed. Subsequent steps work with the line’s current production data.
  • When many records are saved at once, for example through the Web API, the scenario runs once for each record.

On data import

This trigger step pauses the scenario until a specific import task has been executed. Optionally, the trigger can be restricted to successful imports only.

ParameterTypeDescription
Import interfaceMandatoryThe import task that this step listens to.
Start by successOptionalIf enabled, the step only triggers when the import task completed successfully. If disabled, the step triggers regardless of the import result.

On print jobs import

This trigger step pauses the scenario until a print job import task has been executed. It triggers both when a new print job is imported into the database and when an existing print job’s status is reset to pending.

This step has no parameters.

Examples

Example 1: Printing an Imported Print Job

When a print job import task has been executed, the On print jobs import step triggers the scenario. The Send print job to printer step then sends the imported print job to the printer.

Example 2: Printing an Imported Print Job to All Printers

When a print job import task has been executed, the On print jobs import step triggers the scenario. The Identify layout step reads the name of the label layout from the master data, the Generate preview step generates a preview of the print data, and the Send print job to all step then sends the print job to all printers assigned to the line.


On print jobs API request

This trigger step is activated when a print job is received through an external API request. The minimum required information to submit a print job request is the productionLineName field, which identifies the target production line. The printing workflow that follows is configured with coding scenario steps, the same way as a standard print workflow. The API response is returned at the moment the scenario finishes.

This step has no parameters.

Examples

Example 1: Printing All Pending Print Jobs when One Is Requested via API

When a print job request is received via the API, the On print jobs API request step triggers the scenario. The Collect list of print jobs step then collects and triggers all pending print jobs, and the Send print job to all step sends them to all printers assigned to the line. The API response still includes only the print job created by the current request.

Example 2: Printing Only the Requested Print Job via API

When a print job request is received via the API, the On print jobs API request step triggers the scenario. Without a Collect list of print jobs step in the sequence, the Send print job to all step sends only the print job from the current request, and no other pending print jobs are processed.

Limitations

  • If the request is not completed within the configured timeout and a timeout exception is returned, any print jobs and printing results already created up to that point are still persisted in the database; this method is not transactional, so partial results are retained regardless of whether the request completed successfully.

On exception

This trigger step is activated when a preceding step in the coding scenario raises an error. Use it to define the recovery actions that run when a scenario fails, so the error can be handled in a controlled way instead of interrupting production unexpectedly.

ParameterTypeDescription
Coding scenariosOptionalThe coding scenarios this exception handler listens to. If left empty, the handler applies to any coding scenario.
Silent error handlingMandatoryIf enabled, the error is handled silently: no alarm is raised and the user does not receive a toast notification. If disabled, the error is reported as a toast notification is shown to the user.
Exception typeOptionalRestricts the handler to a specific exception type. If left empty, the handler reacts to any exception.

Examples

Example 1: Stopping production on exception

The On exception step is configured to react to the scenario coding scenario, with Silent error handling enabled and the Exception type restricted to Layout not found. When that scenario raises a Layout not found error, the exception is handled silently and the Stop Production step stops the production line.

Example 2: Sending a command on exception

The On exception step is configured with no restrictions: Coding scenarios and Exception type are left empty, and Silent error handling is disabled. As a result, the handler reacts to any exception raised by any coding scenario and reports it as a notification. When an exception occurs, the Send command to device step sends a command to the connected device.


Product or order assigned

This trigger step pauses the scenario until a product or production order is assigned to the production line. It also makes the data of the assignment available to subsequent steps in the scenario: the product, the production order, and the various data linked to the product. If a production order is assigned, the product of that production order is used.

Use this step to prepare the line for the new product or production order, for example to check the label, reset counters, or configure devices, before or instead of starting the production manually.

This step has no parameters.

Examples

Example 1: Checking the Label before a Changeover

At a changeover, the shift lead assigns the next production order to the line. The Product or order assigned step triggers the scenario and makes the product and production order data available. The Identify layout step reads the name of the label layout from the master data of the product, and the Generate preview step generates a preview of the print data with the data of the new production order.

The operator compares the preview with the packaging before starting the production, so wrong master data is detected before any label is printed.

Example 2: Starting a New Order Only on a Cleared Line

When a production order is assigned to the line, the Product or order assigned step triggers the scenario. The Reset counter step sets the selected counter back to its start value, so counting starts fresh for the new production order. The Check I/O step then checks the signal of the line clearance sensor, which reports that no products from the previous production are left on the conveyor. Only if the signal is in the expected state does the Start Production step start the production on the line.

If products are still on the line, the scenario ends at the Check I/O step, and the production is not started. The counter has already been reset. The operator clears the line and starts the production manually.

Limitations

  • The step does not start the production. To start it from the scenario, add a Start Production step, as in Example 2.
  • The step does not look for logistic units associated with the product or production order. To work with logistic units, add a step that selects them, for example Select logistic unit by status.

On production started

This trigger step pauses the scenario until the production line transitions to the started state. It also makes all information linked to the production available to subsequent steps in the scenario — the product, the production order, and any other data associated with the production run.

This step has no parameters.

Examples

Example 1: Printing a Label when Production Starts

When a production is started on the line, the On production started step triggers the scenario and makes the production data available. The Identify layout step reads the name of the label layout from the master data, the Generate preview step generates a preview of the print data, and the Send print job to printer step then sends the print job to the printer.

Example 2: Printing Collected Print Jobs when Production Starts

When a production is started on the line, the On production started step triggers the scenario. The Collect list of print jobs step retrieves a filtered list of print jobs from the master data, and the Send print job to printer step then sends them to the printer.


On production stopped

This trigger step reacts to the stop production event: the scenario is triggered when a production is stopped on the production line.

This step has no parameters.

Examples

Example 1: Resetting a Counter when Production Stops

When a production is stopped on the line, the On production stopped step triggers the scenario. The Reset counter step then sets the selected counter back to its start value, so counting starts fresh for the next production run.

Example 2: Clearing the Print Buffer when Production Stops

When a production is stopped on the line, the On production stopped step triggers the scenario. The Clear print buffer step then clears the pending print data on the selected printer, so leftover print jobs are not printed when the next production starts.


On production paused

This trigger step reacts to the pause production event: the scenario is triggered when a production is paused on the production line.

This step has no parameters.

Examples

Example 1: Setting a Product Status when Production Is Paused

When a production is paused on the line, the On production paused step triggers the scenario. The Set status to products step then sets the configured status on the current products, for example to mark them as on hold while the production is paused.

Example 2: Resetting a Counter when Production Is Paused

When a production is paused on the line, the On production paused step triggers the scenario. The Reset counter step then sets the selected counter back to its start value.


On product reloaded

This trigger step reacts to the reload event on the production line: the scenario is triggered when the active product is reloaded without a production order. It also makes the reloaded production information available to subsequent steps in the scenario. Use On production order reloaded instead for reloads where a production order is assigned.

This step has no parameters.

Examples

Example 1: Printing a Label when the Product Is Reloaded

When the active product on the production line is reloaded, the On product reloaded step triggers the scenario and makes the production data available. The Identify layout step reads the name of the label layout from the master data, and the Send print job to printer step then sends the print job to the printer.

Example 2: Clearing the Print Buffer when the Product Is Reloaded

When the active product on the production line is reloaded, the On product reloaded step triggers the scenario. The Clear print buffer step then clears the pending print data on the selected printer, so leftover print jobs are not printed for the reloaded product.

Limitations

  • The step only triggers when the reload happens without a production order assigned. If a production order is assigned, use On production order reloaded instead.

On production order reloaded

This trigger step reacts to the reload event on the production line, restricted to reloads where a production order is assigned: the scenario is triggered when the active production order is reloaded. It also makes the reloaded production information available to subsequent steps in the scenario. Use On product reloaded instead for reloads where no production order is assigned.

This step has no parameters.

Examples

Example 1: Printing a Label when the Production Order Is Reloaded

When the active production order on the production line is reloaded, the On production order reloaded step triggers the scenario and makes the production data available. The Identify layout step reads the name of the label layout from the master data, and the Send print job to printer step then sends the print job to the printer.

Example 2: Updating the Status when a Production Order Is Reloaded

When a production order is reloaded on the line, the On production order reloaded step triggers the scenario. The Set status to orders step then sets the selected status on the current production order.


On printer log

This trigger step reacts to the arrival of a new printer log entry: the scenario is triggered when a new entry is created in the printer log. It also makes the printer log entry from the event available to subsequent steps in the scenario.

This step has no parameters.

Examples

Example 1: Creating a Logistic Unit from a Printer Log Entry

When a new printer log entry arrives, the On printer log step triggers the scenario. The Create logistic unit from printer log step then creates a logistic unit from the entry, and the Set status to logistic units step sets the selected status on the newly created logistic unit.

Example 2: Reprinting a Label from the Printer Log in a Global Scenario

In a Global scenario, when a new printer log entry arrives, the On printer log step triggers the scenario. The Reprint printer log step then reprints the label from that printer log entry.

Limitations


On reprint printer log

This trigger step pauses the scenario until a reprint is requested from the printer log.

This step has no parameters.


On resource file import

This trigger step pauses the scenario until a resource file import task has finished.

This step has no parameters.