Print from workflows

All physical print actions use a registered Printer. Configure the destination once in Operations Studio, then select it in the workflow. Changing the selected label does not grant permission to configure printers or bridges.

Test a label

1. Open a Label and check its dimensions, DPI and data bindings.
2. Select a registered printer in the print controls. Use a compatible language and stock.
3. Supply representative test data and queue a test print.
4. Open the job and verify its destination, copies and result.
5. Inspect and scan the actual label before publishing or activating a production workflow.

A draft test is an explicit test action. Production jobs use a published label snapshot. Preview example values are not a source of operational material, batch or order data.

Automate an operational event

In a supported Automation, add Print label, select the published Label and registered Printer, set copies and map the required data. For example:

When production is reported, print the finished-part label on Packaging Line 2 using the event's order, material and quantity.

Decide whether the event needs one label per part, one per batch or one per container. A reported quantity of ten does not by itself establish the intended label count. If serial numbers are required, allocate them through the operational process before printing.

Validate the workflow, publish and activate it, then verify one agreed event. Inspect both the Automation run and its print job. Repeated delivery of the same action must not create an extra job with a different identity.

Data and compatibility checks

Every referenced value must exist in the actual job context. Missing required bindings fail the job rather than printing sample values. Printer language, DPI, label dimensions and copies must satisfy the registered configuration. An incompatible job should be corrected before another attempt.

The Label data fields offer the Automation's available source values. Keep From order and event when the label already references the event's normal order/material context, or select a source explicitly for each label field. Explicit mappings override the automatic context and accept scalar text, numbers and booleans. They do not execute expressions or scripts. A missing mapped value stops the action.

Publishing a Print label Automation requires print authority and the production-order, material and work-center read permissions used by its automatic context. The runtime uses its own scoped service identity and checks its current grants. For manual jobs, additional source-read permissions are needed only when Ennea retrieves missing values from those records. Data subject to an active privacy restriction cannot be printed through an Automation or reprint.

When upgrading an existing print Automation, select a registered printer and republish it with the required permissions. Older service grants are not silently expanded; an active workflow without the current delegated authority fails closed.

The bridge receives rendered output and the approved printer reference, not the whole production order. A queued job preserves its own version and values even if the live order or template changes later.

Review and reprint

Use job history for cancellation, expiry and uncertain outcomes. A reprint is a new physical action with a recorded reason and a reference to the original job. It does not overwrite history or create a new business serial number automatically.