Print Job
What is this data
A print job is the unit of work sent to a printer.
Where it is used
A print job is normally created by a coding scenario’s Send print job to printer/Send print job to all step, but an external system (an ERP or WMS, for example) can also create one directly by importing print job data or calling the print-job API. Both paths fire an event that a coding scenario can react to — the On print jobs import and On print jobs API request trigger steps let a scenario automatically start printing as soon as a print job arrives, with no operator scan required. See Send Print Job(s) and Event for the related coding scenario steps.
Because importing a print job can immediately trigger printing, treat a Print Job import task as an operational trigger, not just a data update.
Fields
| Field | Label | Marked mandatory in UI | Actually enforced on import | Notes |
|---|---|---|---|---|
quantity | Quantity | Yes | Yes | Must parse as an integer, or the row is rejected. |
productionLine | Production line | Yes | Yes | Must match the title of an existing production line — production lines are never auto-created. |
productVariant | Product variant | No | Conditional | Checked only when productCode is also supplied; must be 10 characters or fewer. |
productCode | Product code | No | No | Used with productVariant to resolve or create the linked product. |
productionOrder | Production order | No | No | Used, together with the resolved product, to resolve or create the linked production order. |
status | Print Job Status | Yes | — | Always force-set to Pending on import; any value supplied in the row is ignored. |
dateTimeImport | Import date and time | Yes | — | Always force-set to the current server time on import; any value supplied is ignored. |
filenameImport | Import filename | Yes | — | Always force-set to the source file’s name on import; any value supplied is ignored. |
Matching & updates
There is no match key for this table. Every imported row that supplies at least one print-job field always inserts a brand-new print job — Print Job import is append-only; there is no update path, so importing the same source data twice creates duplicate print jobs rather than updating one.
Auto-created related records
If the referenced product doesn’t exist yet, it’s created automatically; if a production order is also supplied and doesn’t exist yet, it’s created too. The production line, however, is never auto-created — an import row referencing an unknown production line fails.
Custom / additional columns
Beyond the fields above, a print job can carry custom columns to describe whatever else your company needs to track about it. Up to 100 custom columns are supported, each storing up to 3200 characters. Print Job has no relation of its own to Various Data — only Product does (see Various Data).