This page lists relevant changes and updates in fiskaltrust's cloud services, on-premise products, and documentation.
You can subscribe to all changelogs via RSS, follow the GitHub repo, or display categories of changes by tags.
In this version of the Middleware, we've added the possibility to declare a 'Master Queue' if there are multiple Queues connected to one TSE, in order to avoid long timeouts during daily closings and have one tar file export for all queues.
In this version of the Middleware, we now automatically clear up old tar files in the fiskaltrust/service/Exports/ folder.
In this version of the Middleware, we've added a warning dialog when clearing app data and a prompt for disabling battery optimization in the Android Launcher. Additionaly, we've fixed the notification in the the Android Launcher and a bug when sending empty cbReceiptReferences to the Middleware.
In this version of the Middleware, we updated the FCC used in the SwissbitCloud and DeutscheFiskal SCUs to protect against Log4Shell exploits.
In this version of the Middleware, we introduced compatibility with the upcoming fiskaly v2 standalone product and implemented some fixes that should improve the runtime behavior of the Middleware, especially when using the CryptoVision TSE or in cases our users experienced memory or performance issues. Additionally, we've updated the Ambassador stack in Bring your own Datacenter to support new Kubernetes versions. Please make sure to read the Migration Guide before updating.
In this version of the Middleware, we added the possibility to update the firmware of Swissbit TSEs. Additionally, some minor issues in the DSFinV-K were resolved and we improved logging for the Fiskal Cloud Connector.
The focus of this sprint was improving the overall user experience of the Shop/Products page and the german scu selection.
In this quality-of-life release of the Middleware, we resolved several issues that were occurring for segments of our users, and introduced multiple stability improvements to further improve the behavior of the Middleware during implementation and runtime.
In the past weeks we have been hardly working on creating the Technical Rollout which should help our customers to rollout Middleware configurations similar as they are currently rolling out products with the Rollout Management.
In this past Sprint, the main focus was the scaled rollout for the french market and general user experience improvements.