On September 24th, 2024, we published Mustangserver 1.4.1, which offers a improved document type recognition as well as ZUGFeRD 2.3.0 support with it’s corrected validation. Additionally, the manual has been extended, e.g. with a list, where in the JSON which BT IDs are passed.
Mustangserver 1.4.1 has become the new default version if a request on api.usegroup.de does not specify a particular version preference.
Month: September 2024
Mustang 2.14.0
Mustang 2.14.0, released on September 23rd, 2024, improves validation by supporting ZUGFeRD 2.3.0.
Fixes
- #467 Fix test using wrong file
- #468 Fix validator dependencies
- #482 Fix current validation errors
- #423 can no longer add attachments via cli
- #465 cli version should also be able to combine PDF/A-3 source
- #472 Fix logging implementation missing in CLI
- #471 Fix LegalOrganisation schemeId
- #473 Fix UnsupportedOperationException in buildNotes
New Features
- #456 Provide a way to set uriUniversalCommunicationId on the TradeParty using JSON deserialization
- #461 UBL import contacts
- #463 add support for BT-33, i.e. Tradeparty description #463
- #469 Enable EN16931 schema validation for XRechnung
- #476 Add DesignatedProductClassification for SpecifiedTradeProduct
- #487 update to zugferd 2.3.0
Mustangserver 1.4.0
On September 2nd we released Mustangserver 1.4.0 which now features the possibility to extract files embedded in invoices, and allows to convert invoices not only to HTML but also to PDF.
Mustangserver is the REST API which provides functionality from the Mustangproject library, which it is based on, and more. Since Mustangproject has been upgraded to 2.13 in the background, some fixes, like an improved conversion of UBL to HTML, or the removal of due date as de facto required field, are now also taking affect, additionally to the fixes immediately applied to Mustangserver: two fixes concerning article description as well as an improved manual, which now also features instructions how to use Mustangserver in conjunction with C#.
Mustangserver 1.4.0 can already be specifically selected and will become default for operations without specified versions at the next planned maintenance on 28 September.