What RIOMA does with the M3 job
The print job stays the starting point. RIOMA creates the document and sends it through the channels the job names.
Your print jobs stay the starting point
You keep creating the jobs in M3. RIOMA reads the print XML and prepares it for that document. Output follows the Media details in the job.
The format depends on the document
Business documents are produced as PDF. Matrix and list reports can be PDF or, for mail and archive, an Excel file. Excel applies only in that report context. ZPL is available for the labels MWS450 and MWS485, not for other programmes.
Technical detail
If M3 marks Excel or CSV on a business document, the output stays PDF. For reports, mail or archive becomes an xlsx file, not a CSV text file. Print of a report stays PDF.
ZPL covers MWS450 (put-away) and MWS485 (package and logistics), in a rough 4×6 inch layout. Print writes the file without SMB. A send to a Zebra printer runs only when a host is set. If only that connection fails, the file remains and the job counts as produced.
Business-document templates are LaTeX. There is no visual drag-and-drop designer.
Created is not the same as delivered
Print, email and archive follow the job. An OK back to M3 means the document was created. Delivery can still be running or fail afterwards. There is no automatic retry. SFTP is not a Media type in M3, applies only to archive jobs and is off by default.
Technical detail
SFTP needs an archive block and a routing rule that names a target. The rule can keep the archive as well, or replace it. The host-key fingerprint and credentials must be set.
PDF print writes a file and, when credentials are set, can send it over SMB to the printer address in the job.
A later failure of email, archive or SFTP does not change the OK sent to M3. If M3 sends the same job again, every channel runs again, including those that already succeeded.
Layout changes on the next job
RIOMA rereads templates and part of the document and division rules on the next job. That does not need a restart. Routing, SMTP and some rules apply only after a process restart.
Technical detail
Reread on the next job: .tex templates, documents.yaml, the division rules in rules.yaml, field labels and translations.
Applied after a process restart: steering.yaml, sftp_routing.yaml, output.yaml, SMTP environment variables and the cached Swiss QR rule.
One template, several companies
The same template can switch logo, address, footer and conditional text by M3 division. Field labels can follow the language of the document. If there is no valid division and no default configuration, the job is rejected.
Technical detail
Language comes from M3 fields such as OALNCD or DocumentLanguage.
A failure stays with that job
One failed job does not stop the jobs that follow. Errors during creation and errors during later delivery are recorded separately. The optional dashboard shows counters for one installation, not a history of every delivered document.
Technical detail
Creation errors: M3 receives ERROR. The XML and the error text are stored under output/failed/.
Delivery errors after a successful creation are stored under output/failed_delivery/.
The dashboard runs in the same process and is off by default. With a username and password it shows today's counters and the last seven days. The original XML of a failed job sits behind its own link.
Jobs can be traced through the M3 job number and an internal id.