November 2025 Release Hotfix 1
This hotfix for the November 2025 release includes several fixes for eTASK payment transactions as well as other bug fixes.
Please check the change log to see if the changes are relevant to you. It is not necessary to install the November 2025 release in advance; the updates are cumulative.
eTASK SmartReportViewer
Bug Fix: Error Message in Smart Report Viewer
A bug has been fixed that caused the Smart Report Viewer to display a message about missing permissions in certain scenarios when the logged-in user was a system administrator.
eTASK BIM
Bug fix: PDF export from the BIM Explorer
The PDF export from the BIM Explorer displayed an error message with the November 2025 release. The export now works as usual again.
eTASK Payment Transactions
Bug fix: Bulk transfers are sent as individual transfers
Occasionally, batch transfers in eTASK Payment Transactions would create a single batch per invoice, causing the bank to process them as individual transfers. This behavior has been resolved.
eTASK Vehicle Booking
Bug fix: Terms of Use for Vehicle Booking
(Customer Reference: CAFMCAB-411)
The terms of use in vehicle booking now always open in a new browser tab rather than in a portal tab. This makes it easier to handle documents stored on pages with restrictive configurations.
eTASK FM Portal
Bug Fix: Sample Report for Door Signs - QR Code Output
(Customer Reference: INC000007093401)
An error related to the sample report for door signs "Door Sign Basic" has been fixed; previously, the generated QR code always pointed to the eTASK development system.
Bug Fix: Unknown Dynamic Attributes in Excel Import
A behavior has been modified that previously allowed the use of Excel import templates containing a dynamic attribute unknown to the target portal. Such a file is now rejected with the corresponding message.
Bug fix: Truncated codes for parking spaces
(Customer Reference: CAFMCAB-352)
The automatically generated codes for parking spaces now use the full location code and no longer truncate it to the first 10 characters.
Bug Fix: Resubmission after Contract Extension
An unintended change occurred with the modification of the date calculation for contracts. When a contract was extended, a follow-up date was automatically set 14 days before the end of the notice period. This overrode existing entries for the follow-up. The function now no longer sets a follow-up date, as intended. Are you familiar with contract events? These offer a follow-up function with history and documentation.
Improvement: Workflow Implementation
To make the setup of workflows easier and more transparent for you, each role assignment now includes a "Dynamic Role Assignment" checkbox that indicates whether you need to handle the assignment of this role yourself or whether the assignment is based on the content of the relevant data. Thank you very much for this simple and effective suggestion for improvement!