Integration example · not a certified ServiceNow Store app
Asset labels from a ServiceNow workflow.
Keep an approved LBX template, bind a controlled asset payload, inspect the rendered label, and hand it to an explicitly chosen local print path.
Six deliberate fields
- asset_id
- AST-20481
- serial_number
- SN-DEMO-8842
- owner
- Alex Example
- location
- Munich Test Lab
- support_group
- Workplace Demo
- qr
- example.invalid/assets/AST-20481
Example request
POST /v1/render
{
"templateId": "asset-label",
"fields": {
"asset_id": "AST-20481",
"serial_number": "SN-DEMO-8842",
"owner": "Alex Example",
"location": "Munich Test Lab",
"support_group": "Workplace Demo",
"qr": "https://example.invalid/assets/AST-20481"
},
"format": "png"
}
What this example proves
Named field discovery and binding, deterministic SVG/PNG rendering, and a clear hand-off boundary to a printer transport.
What it does not prove
ServiceNow certification, complete b-PAC compatibility, printer online state, loaded media, or a successful physical print. Those require the agreed customer environment and real hardware.
Test the templates you already use.
A compatibility review identifies fields, warnings, output geometry, and the smallest viable pilot path.