Print Subscriptions
Print Subscriptions enable automatic printing of BC reports after specific posting events — without manual intervention. For example, when a sales shipment is posted, the shipment report can be automatically printed on the warehouse printer.
Opening the Page
- Via search: Print Subscriptions
- Via the Print Service Dashboard → Subscriptions
- Via the Print Service Setup → Print Subscriptions
How It Works
BC Posting Event (e.g. Sales Shipment Post)
↓
Event is raised
↓
Print Service checks: Are there active subscriptions for this event?
↓ Yes
Report is rendered as PDF → Print Job in Queue → Print via ECIService
Each subscription defines: - Which event triggers printing (Trigger) - Which report to print - Which printer to use - How many copies
Subscription List
Fields
| Field | Description |
|---|---|
| Entry No. | Sequential number (automatic) |
| Description | Descriptive name for the subscription (e.g. "Shipment Warehouse 1") |
| Trigger Event | The BC event that triggers printing (see Trigger overview) |
| Report ID | The object ID of the BC report to print |
| Report Name | Name of the report (auto-filled) |
| Printer Code | Target printer. Empty = Default Printer from setup |
| Copies | Number of copies (1–99, default: 1) |
| Enabled | Whether this subscription is active |
Actions
| Action | Description |
|---|---|
| Enable All | Enables all subscriptions |
| Disable All | Disables all subscriptions |
Subscription Card
Detailed configuration of a single Print Subscription.
Fields
| Field | Description |
|---|---|
| Description | Freely chosen name for identification |
| Trigger Event | The triggering BC event (dropdown, see below) |
| Report ID | Report object ID. Use lookup to browse all available reports |
| Report Name | Automatically filled after selecting the Report ID |
| Printer Code | Target printer (optional — empty = Default Printer) |
| Copies | Number of print copies |
| Enabled | Enables/disables this subscription |
Available Trigger Events
| Trigger | Description | Typical Report |
|---|---|---|
| After Post Sales Shipment | Raised after every sales shipment posting | Sales - Shipment (208) |
| After Post Sales Invoice | Raised after every invoice posting | Sales - Invoice (206) |
| After Post Sales Credit Memo | Raised after every credit memo posting | Sales - Credit Memo (207) |
| After Create Shipment Label | Raised after creating a shipping label | — (Label is printed directly) |
| After Post Warehouse Shipment | Raised after posting a warehouse shipment | Warehouse Shipment |
| After Post Transfer Shipment | Raised after a transfer posting | Transfer Shipment |
| After Post Purchase Receipt | Raised after a purchase receipt | Purchase - Receipt |
Configuration Examples
Scenario 1: Automatic Shipment Printing
| Setting | Value |
|---|---|
| Description | Auto-print shipment |
| Trigger Event | After Post Sales Shipment |
| Report ID | 208 (Sales - Shipment) |
| Printer Code | PDF-OFFICE |
| Copies | 2 |
Scenario 2: Warehouse Receipt Label
| Setting | Value |
|---|---|
| Description | Receipt label |
| Trigger Event | After Post Purchase Receipt |
| Report ID | (customer-specific report) |
| Printer Code | ZPL-WH1 |
| Copies | 1 |
Scenario 3: Invoice Printing
| Setting | Value |
|---|---|
| Description | Invoice PDF |
| Trigger Event | After Post Sales Invoice |
| Report ID | 206 (Sales - Invoice) |
| Printer Code | PDF-ACCOUNTING |
| Copies | 1 |
Notes
Multiple Subscriptions per Event
You can define multiple subscriptions for the same event — e.g. print the shipment report on the office printer AND a warehouse label on the Zebra printer.
Report Must Be Printable Without Input
The report is rendered without a print dialog (silent). Make sure the selected report does not require mandatory request page parameters that need interactive input.
Routing Rules Still Apply
If no Printer Code is specified in the subscription, the normal routing logic applies (Print Rules → Default Printer → Fallback).
Disable Instead of Delete
If a subscription is temporarily not needed (e.g. during a system update), disable it via the Enabled field instead of deleting it. This preserves the configuration.