Release 26.5.40 on 19.06.2026

This release rebuilds the OpenTRANS 2.1 invoice export on a hardcoded rule set, adds a notification when an outbound job's document filter matches nothing, and fixes an OpenTRANS/Cegedim send that could stay stuck in "Running" forever after a server error.

Feature

• The OpenTRANS 2.1 export (ot:INVOICE, version 2.1) is now generated from hardcoded builders inside the Exp.OpenTrans codeunit instead of the schema-driven XML engine. Sales invoices, sales credit memos and issued reminders each have their own builder assembling the INVOICE_HEADER → CONTROL_INFO → INVOICE_INFO structure: GENERATOR_INFO = mseDoc365, GENERATION_DATE from the document's Last Export Date, and the currency taken from the document with a EUR fallback. Invoices and credit memos emit the buyer, invoice issuer (Company Information, party id 00000) and invoice recipient parties; reminders emit the recipient only. The "emit when non-empty or mandatory, self-close mandatory-but-empty" rule from the engine is preserved. The previous schema-line definitions are left in place but dormant
• Running an outbound job from the mseDoc365 Job card now shows an information message when the job's document filter matches no documents, instead of ending silently with no feedback. The message reflects the filter the user actually set and is suppressed for background Job Queue runs, so unattended processing stays silent

Bugfix

• Sending an OpenTRANS document to Cegedim no longer leaves the eDocument stuck in "In Progress" / Running when the server returns an error or is unreachable. The status call's result is now checked: when the call fails or the response carries no invoice status, an error is raised (carrying the underlying message) instead of silently defaulting to "In Progress". The error propagates out of the polling loop through the fail handler, which marks the eDocument and step Failed and stops the process, rather than polling every 15 seconds indefinitely