September 15, 2021
In this version of the Middleware, we added the possibility to easily identify mandatory and optional signature items when printing receipts. Additionally, the Middleware is now able to automatically update the Fiskal Cloud Connector, and several bugs and stability issues have been resolved. This release also marks the first non-RC version of the FiskalyCertified SCU (which added support for fiskaly's certified version 2).
Version 1.3 of the Middleware is meant for the German market only, customers in Austria and France should continue to use version 1.2. We will unify these experiences in an upcoming version.
Starting with this version, we're adding the ftSignatureFormatFlag
0x0000000000010000 to signatures that are not mandatory to print. Especially with the recently changed KassenSichV regulations in Germany (which allow to omit printing most texts when a QR code is added), this should enable PosCreators to more easily decide which information needs to be printed onto the receipt and which information is optional.
More information can be found in the respective docs.
Please note that this behavior can be deactivated by setting the Queue configuration parameter
Starting from this version, each SwissbitCloud and DeutscheFiskal SCU version is tied to a specific minimal Fiskal Cloud Connector (FCC) version. If the currently installed FCC version is lower than this, the Middleware will automatically download and update the newer FCC. This should enable users that have already installed previous versions to profit from the latest improvements in this external dependency.
We've made the HTTP timeout and the used HTTP proxy configurable when using the FiskalyCertified SCU for fiskaly's v2 TSEs. The following parameters have been added:
FiskalyClientTimeout(in milliseconds, default:
ProxyUsername(leave empty for anonymous access)
ProxyPassword(leave empty for anonymous access)
0x0000000020000000, which removes open transactions from our database that are already marked as closed on the TSE, is now also supported in zero-receipts (previously, this was only the case for daily-closing receipts). This should enable Middleware users to escape rare cases in which e.g. the TSE's answer got lost, but the request to the device or service was actually processed.
Our Bring your own Data Center solution now supports SwissbitCloud and DeutscheFiskal TSEs using self hosted FCCs. To make use of this, the Fiskal Cloud Connector should be installed on a machine or container in the same network, and the SCU configured to use it via the
FccUri configuration parameter (more details in our docs).
We've fixed an issue where the connection string to custom Redis instances would be assembled wrongly.
We've fixed three issues in our DSFinV-K exports that could occur in some edge cases:
UMS_BRUTTOwas calculated wrongly when discounts were sent in a specific format
REF_BON_IDwas incorrectly set to the value of
ftReceiptIdentification(only applied to local exports, Portal exports were not affected)
- Some timestamps in transactions.csv were not written in UTC, but in the local timezone (only applied to local exports, Portal exports were not affected)
We've fixed an issue where the new FiskalyCertified SCU wrongly returned an empty certification ID instead of the correct value
We have created documentation templates for the mandatory process documentation (Verfahrensdokumentation), in which we describe how the Middleware populates specific fields in the DSFinV-K export, and how exports can be downloaded from the Portal if the users bought a PosArchive package. This template can be added to the PosCreator's or PosDealer's process documentation and might be useful in case questions occur during audits.
It's available in the German Portal's download section.
Packages not listed here were not updated, as we decided to not increase the version of unchanged packages. All packages with versions greater or equal to 1.3.1 are compatible with each other (it is e.g. possible to use fiskaltrust.Middleware.SCU.Swissbit.1.3.1 with the new queue packages).
- fiskaltrust.Middleware.Queue.EF v1.3.23
- fiskaltrust.Middleware.Queue.MySQL v1.3.23
- fiskaltrust.Middleware.Queue.SQLite v1.3.23
- fiskaltrust.Middleware.SCU.DE.FiskalyCertified v1.3.23
- fiskaltrust.Middleware.SCU.DE.SwissbitCloud v1.3.23
- fiskaltrust.Middleware.SCU.DE.DeutscheFiskal v1.3.23
We will focus on further increasing the Middleware's stability and performance in the upcoming sprints. As always, we're happy to hear feedback and suggestions via email@example.com or directly via issues in our GitHub repositories.