With Hotfix 3 for the March 2026 release, we are fixing several additional bugs in the current release.
You need this hotfix if you:
Have issues exchanging data with certain banks
Create orders and order plans in Plant Maintenance with high object turnover
Set up workflow substitutions with a duration of one day
Use dynamic characteristics of the Date type
cannot create new work centers
Due to an error in the deployment of Hotfix 3 from May 29, 2026, in the Customer Center, you are receiving this information again today.
eTASK.FM Portal (1000)
Bug Fix: Dynamic Features of the "Date" Type
An error has been fixed whereby dynamic attributes of the "Date" type did not retain their entered value when saved.
Bug Fix: Filtered Views for the Data Update Import Template
A bug has been fixed where data update templates sometimes displayed an error message if the list from which they were called was filtered.
Bug Fix: Creating Workstations is Possible Again
A bug has been fixed that prevented the creation of new workstations due to a misconfiguration.
Bug fix: One-day workflow substitutions enabled
A bug has been fixed that prevented workflow substitutions with start and end times on the same day from being processed.
Improvement: Error handling when importing plug-ins
Installed plug-ins that are reinstalled with every update now forward their error messages to portal administrators if they cannot be reinstalled.
eTASK internal only: ✅ Fix for: PostUpdate in Beta and Hotfix fails
eTASK.Maintenance (1070)
Bug fix: Object selector in work order plan and work order
The object selector for maintenance orders and order plans has been adjusted so that old entries do not remain "stuck" in the cache while new ones are only partially added.
eTASK.Payment Transactions (1225)
Bug fix: Resolution of compatibility issues with EBICS payment transactions
Resolution of compatibility issues with EBICS payment transactions with certain banks (Postbank, Deutsche Bank). The automatic version assignment to EBICS 3.0 has been disabled, so that the version supported by the bank is used automatically.
Additionally, EBICS communication logging has been improved: Errors and trace information are now stored in detail in the bank transaction log, which facilitates error analysis in the event of connection issues. Furthermore, other compatibility issues have been resolved.