January 2024 Release, including Hotfix 1
This version replaces the January 2024 release dated January 19, 2024. If you have not yet installed the release, please note the following information.
If you have installed the January 2024 release, you should also install the hotfix if you are experiencing issues with the Outlook add-in in your environment.
Important Notes
Supported Microsoft SQL Server Versions
!! Due to a technical change, this release cannot be installed on SQL Server 2016.
We continue to support SQL Server versions 2017, 2019, and 2022. Do you need assistance with the migration? Please feel free to contact our Projektteam@etask.de!
Note regarding Microsoft SQL Server Express Edition
Some new features require the use of SQL Server Express Edition with Advanced Service. If you are only using SQL Server Express Edition, please contact us at Projektteam@etask.de for assistance with the migration to Advanced Service.
Users of the eTASK app for Windows
With the release of this update, a current version of the eTASK app has also been released in the Microsoft Store. Please note that this current app version is compatible exclusively with the latest release version of the portal; that is, both the portal AND all connected mobile devices must be updated.
Therefore, please update your mobile devices only if you also plan to update your portal to the current release at the same time. If this is not desired or possible, please disable the automatic installation of updates for the eTASK app on your devices. Please note, however, that after a previous update of your portal, your devices must also be updated to the current app version.
Please make sure to sync your mobile devices before the update.
Users of the eTASK Add-in for Revit
With the release of this update, a current version of the eTASK Add-in has been made available in the Customer Center. Please update your eTASK Add-in for Revit to the latest version.
eTASK.Onboarding
Improvement: Onboarding contact person is continuously verified
There is a contact person for every onboarding process. This is either the supervisor or a person selected as a substitute. Previously, this field was automatically filled in when creating the onboarding process. We have now expanded this process for you. Even after the process is created, the system regularly checks whether the onboarding contact person and the supervisor or deputy remain the same. If there is a change, the new person is automatically assigned as the contact person.
eTASK.BIM
Improvement: Tomcat update to the latest version
We use Apache Tomcat on the eTASK.BIM server. With this release, the latest version 9.0.82 is now in use there.
See also 📄 eTASK.BIM IC2638
eTASK.MyApp/Inventory
Support Information: Improvement to image transfer between FM Portal and Inventory App
Due to a Windows update, it is now necessary to adjust the image crop once when taking a photo in the eTASK.WinApp/Inventory so that the "Save" function becomes active. This inserts the image into the match code, room, or object. The synchronization of images between the app and the portal has been improved to prevent multiple images from being incorrectly stored per match code.
See also: Conducting an inventory with mobile devices
eTASK.DigitalArchive
Improvement: Easier transfer of data to a new document
With this release, you can easily and conveniently transfer data from your existing documents to others. This is possible for documents that you have imported into your eTASK.FM portal via the document upload feature of your Digital Archive. To do this, copy an existing data record using the copy function in the toolbar of the open document, make the desired changes to the copied document, and save the data record. You will then find an upload option in the "Download Linked File" section, which you can use to attach the desired file to the document.
See also: Manage Digital Archive
eTASK.Dunning
Bug Fix: Issue with displaying outgoing invoices with multiple dunning stages resolved
There were briefly issues with outgoing invoices that had gone through multiple dunning stages. For each dunning stage, the invoice was displayed once in the list of outgoing invoices. We have promptly resolved this issue, so that now, as usual, all your outgoing invoices are displayed only once, regardless of the number of dunning stages they have gone through.
See also: Dunning
eTASK.Outlook Room Booking
Bug Fix: Authentication Issues with the eTASK.Outlook Add-in
Due to a technical change, there were temporary issues logging in to the eTASK.Outlook add-in. We have fixed this issue for you in this release, so you can log in to your eTASK.Outlook add-in as usual.
Improvement: Enhanced security for authentication via Azure Active Directory
We prioritize your security. With this release, when setting up login via Azure Active Directory, it is necessary to store both the AZURECLIENTID and the AZURETENANTID in the system configuration. This helps prevent unauthorized access via manipulated authentication tokens.
See also: Registering OAI App from Microsoft Entra ID in eTASK
eTASK.Vehicle Booking
Bug Fix: "Contact Person for Vehicle Reservation" is displayed again
There was a temporary issue with vehicle reservations. Even if contacts for vehicle reservations were maintained via the selected location, they were still not displayed in the vehicle reservation. We have fixed this issue so that all assigned contacts are displayed again.
See also: Vehicle Booking
Bug fix: Deactivated Infrastructure Building Management form (Vehicle Booking)
Under Infrastructure Building Management - Fleet Management - Vehicle Booking - Vehicle Bookings, a form could be filled out using the New button in the toolbar, but an error occurred when saving. Vehicle bookings are actually only supposed to be reserved via MyFM - Order Services. With this release, clicking the New button opens a form, but no functionalities are available in the toolbar.
See also: Booking Vehicles
eTASK.Operating Cost Settlement
Bug Fix: Incorrect calculation of amounts in operating cost statements fixed
When generating operating cost statements, issues arose with the calculation of advance payments, particularly in distinguishing between actual advance payments and target advance payments. This issue has been resolved, so that with this release, all advance payments are once again calculated correctly according to their settings.
See also: Operating Cost Statement
Improvement: Documents for operating cost statements now clearer
In your eTASK.FM portal, you have the option to download the documents for your operating cost statements as a PDF file. With this release, we have made this file clearer for you. The order in which invoices and documents are displayed now follows the invoice items in your operating cost statement.
See also: Consolidate all invoices from a billing period into a single PDF
eTASK.Cost Entry
New Feature: New functions related to transfers
With this release, many new features related to journal entries are now available to you. When creating a journal entry, you can now choose whether it should be assigned to a customer, a vendor, or a general ledger account. Receivables created in this way are also listed in the OPOS list (Open Customer Accounts) and the tenant’s bank statement. Additionally, bank entries can be assigned to open transfer postings. This documents payments for transfer posting amounts and allows the transfer postings to be closed. They are then transferred to the posting journal. IMPORTANT for customers who already use journal entries: Previously, amounts for journal entries involving customers had to be entered as negative. Since you now select whether a journal entry involves a customer when creating it, this is no longer necessary, and you can enter the amount as a positive amount as usual.
New Feature: New Specific Allocation Rules for Payments
Recurring liability outgoing invoices in automatic payment allocation have been adjusted: The invoice date is taken into account in the payment reference so that invoices created from the recurring liability can be allocated when the original invoice number is specified.The uniqueness scheme for payment allocation has been expanded to include the following rule: Invoice number -> is recognized as the source of the recurring liability invoice (created from an invoice) -> the total amount is checked from the filtered invoices + the invoice date listed in the payment reference in the following format: dd.mm.yyyy
See also: Cost Entry
New Feature: Data Query via REST API Expanded to Include Open Items
The list of open items for customers can now also be queried via the API and is thus available for other applications.
See also: eTASK API
New feature: Prepaid and accrued expenses
With prepaid and accrued expenses, you can distribute an annual invoice (expense or revenue) evenly over a desired period. This allows for a better assessment of the profitability of individual months. Perform the accrual directly during invoice entry.
Bug fix: Assignment of rights for incoming invoices
There was an issue with configuring permissions for incoming invoices, which temporarily prevented permissions from being assigned to individual information areas. We have resolved this issue. You can now assign permissions per information area again. Please note that permission assignment can be influenced by settings in the workflow. In this case, manually configured permissions are overridden by permission settings from the workflow.
See also: Assigning permissions for menus, info areas, and API paths
Bug fix: Invoices resulting from a recurring invoice are created correctly
Under certain circumstances, invoice documents from recurring invoices could be created twice. This is now correctly prevented.
Bug fix: Cost center can be selected again in the cost distribution key
In the Object Accounting/Cost Entry section, the cost center could not be selected in the cost distribution key. Clicking the combo box displayed an error message. This issue has been resolved.
See also: Cost Entry
Bug fix: Display of transfers in the Open Items - Accounts Receivable report
Transfer postings with a negative sign were posted correctly but were shown as receivables in the open items for accounts receivable. This error has been fixed.
Bug Fix: Issue with Selecting Cost Centers in the Cost Allocation Key Resolved
When creating a new cost center type in the cost distribution formula, there was an issue with selecting the cost center. This issue has been resolved with this release, and the function can now be used again without restrictions.
Bug fix: Display of incorrect amounts after using deviating invoice items fixed
You can create recurring invoices with recurring invoice items for your incoming invoices. If these invoice items temporarily display different amounts, you can use the function for deviating invoice items.When using these deviating invoice items, a temporary error occurred where the amount was displayed for all subsequent scheduled recurring invoices, even if the amount of the standard invoice item was calculated again. We have quickly resolved this issue for you, so that the actual calculated amounts are now displayed as usual in the preview of the scheduled recurring invoices.
See also: Create recurring invoice
Improvement: XRechnungen expanded to include the order number
When creating XRechnungen from the eTASK.FM portal, order numbers from associated orders or job numbers from associated jobs are now also included. This information is automatically inserted into the "BT-13" field when an order or job is associated with the invoice.
See also: Set up XRechnung
Improvement: Cancellation files for electronic invoices improved
When you cancel an electronic invoice in your eTASK.FM portal, a corresponding XML file is generated for download. This file now includes the word "Cancellation" in the file name, making it easier to distinguish from and associate with the original invoice.
See also: Setting up XRechnung
Improvement: Improvement in the cancellation of outgoing invoices
When canceling an outgoing invoice, a cancellation document is created for that invoice. With this release, this cancellation document no longer contains the document number of the canceled outgoing invoice, as was previously the case, but rather the invoice number.
See also: 📄 Rechnung stornieren IC1432
Improvement: Simplification of Reversals for Transfer Postings
If you reverse a posting after a financial accounting export has already taken place, a reversal posting and a corrected posting are created. Previously, however, only the corrected posting was included in a subsequent export, and the reversal posting remained in the system as "unposted." We have now improved this process so that both entries are automatically included in the financial accounting export and processed accordingly. Additionally, we have improved the posting of payments to outgoing invoices. From now on, the invoice number of the outgoing invoice will be displayed in the document field of the posting, instead of the posting month as before. This makes the entry clearer and easier to identify. We have also made journal entries clearer for you. Previously, they included the word "journal entry" in the description. We have now replaced this with the fields "Document 1" or "Document 2." This gives you a better overview of your journal entries as well.
See also: The Financial Accounting Export
Improvement: Update of XRechnungen processing to version 2.2
With this release, your eTASK.FM portal can now also process XRechnungen in the new version 2.2.
See also: Setting up XRechnung
Improvement: Improved automatic payment allocation
With this release, we have improved our automatic payment allocation so that it covers even more scenarios. If there are payments for invoices with the same invoice number, the system searches for the vendor or customer. Previously, allocation was not possible if a company was created as both a vendor and a customer and had the same bank account information. From now on, the system first searches for invoices from the vendor and uses them for allocation if applicable. If no matching invoice is found, the payment is allocated to the customer.
See also: Create assignments automatically
Highlight: QR Code for GiroCode on Outgoing Invoices
With this release, we’re giving you the option to decide whether you want to include QR codes on your outgoing invoices that allow for convenient payment via GiroCode. The QR code contains all payment-related information for your invoice, which can then be imported into the payment system without manual entry. Activate the system parameter "PRINTGIROQRCODE" to enable this feature for your eTASK.FM portal. If you make changes to your invoice, the QR code is automatically updated as well. The bank details contained in the QR code are either the bank details stored for the company or those you have manually entered for the outgoing invoice.
See also: Outgoing Invoices
eTASK.Rental
Bug Fix: Fixed an error in the "Tenant Account Statement" report
There was previously an issue in the "Tenant Account Statement" report when individual items had identical descriptions. They were then grouped together but not correctly included in the calculation. We have now resolved this issue so that all items are included in the calculation regardless of their description.
See also: Report: Tenant Account Statement
Improvement: Improved calculation of the base rent factor per square meter
With this release, the calculation of the m² factor takes into account the total costs of the base rent, including surcharges and rents for parking spaces, and divides them by the total rental area. This ensures that all costs except for operating costs are included in the calculation.
Improvement: Improved allocation of rent payments
Previously, rent payments received in a given month were fully posted to that month, even if they exceeded the outstanding balance. With this release, only the portion of the payment corresponding to the amount outstanding for that month is allocated to the month of the transfer. Additional payments are allocated to other months if there are outstanding balances in those months.
See also: Create allocations automatically
Improvement: Improvement to the "Remaining Term of Lease Agreements" report
In your eTASK.FM portal, you can view the remaining terms of all your lease agreements in a report. If you manage multiple companies in your FM portal, this report previously always displayed a blank page between companies. We have now made this report clearer for you and removed the blank pages. Each new company starts on a new page.
See also: Report: Remaining Term of Lease Agreements
eTASK.Media Supply / Energy
Bug Fixes: Minor issues in various reports resolved
In some reports in eTASK.Energy Consumption Billing, there were issues with the thousands separator in numbers and missing units. We have resolved these issues with this release, so all reports can now be used without errors.
See also: Reports in eTASK.Utility Supply / Energy
eTASK.Warranty
New Feature: Expansion of the Defect List to Include Objects
With this release, we have expanded the defect documentation for you to include the assignment of objects to a defect. In addition to building components or the option to freely describe defects, you can now also use eTASK.Warranty to document defects in objects.
See also: Warranty and Defect Management
eTASK.Open Spaces
Bug fix: "State" field converted to a dropdown menu
The "State" field in the "Property" table in the property cadastre was incorrectly created as a numeric field. It has been converted to a combo box, meaning states can be selected from a list.
See also: The Real Estate Cadastre
eTASK.Service Ticket
New feature: New master list for service tickets
(Customer reference: CAFMBT-115)
In your eTASK.FM portal, so-called master lists are available for various forms. These contain a wealth of relevant data and allow you to create your own overviews, e.g., by using the filter options.With this release, we have created a new "Service Tickets" master list for you. It contains all possible information related to your service tickets. You can find the new master list in your portal under "Infrastructural Facility Management - Service Ticket - Reports - Service Tickets Master List".
eTASK.Maintenance
Bug Fix: "Maintenance Orders" Tile Corrected
When displaying the "Maintenance Orders" tile on the dashboard, an error occurred if maintenance had not yet been put into operation and there were no maintenance orders. Additionally, it was still based on an outdated static workflow. This has been fixed.
See also: Dashboards
Improvement: Rejected orders now included in acceptance checks and the maintenance plan
With this release, rejected orders are now also taken into account and marked in the acceptance inspection reports and in the maintenance plan in eTASK.Maintenance. In the maintenance plan, orders with a defect are now marked in red, while rejected orders are marked in blue.
See also: Reports in eTASK.Maintenance
eTASK.FM Portal
New Feature: Master List Extensions
(Customer reference: CAFMBT-115)
In your eTASK.FM Portal, so-called master lists are available for various forms. These contain a wealth of relevant data and allow you to create your own overviews, e.g., by using the filter options. With this release, we have expanded the "People & Rooms" master list to include the states where the individuals are based. The state is automatically updated via the corresponding building or through the assignment to a location based on the room assignment. You can access this information via the Advanced Excel Export.
New Feature: New Form for Planned Location Occupancy
(Customer reference: CAFMBT-132 & CAFMBT-234)
With this release, a new form is available in your eTASK.FM portal that allows you to create and maintain an overview of the planned occupancy of your locations. To do this, assign the companies and departments that are to occupy your locations in the future.
New feature: New workflow for HSE managers
We have created a new workflow for you that informs HSE officers about changes to their rooms. Additionally, semi-annual updates and reminders regarding their rooms are sent to the HSE officers. This ensures that all your HSE officers are always up to date.
See also: Managing functions with coordinators and representatives
New feature: Improved use of the tab bar
In your eTASK.FM portal, you can have multiple tabs open. These are displayed in the tab bar. With this release, tabs can be moved within the tab bar. This allows you to arrange your tabs in a way that works best for you. Additionally, new tabs always open next to the active tab, so you can easily navigate between them.
See also: The tab bar
Bug Fix: Issue with Workflow Permissions Resolved
For a short time, users with administrative rights or write permissions for workflows were able to edit records even if they did not have a role in that workflow. We have immediately fixed this bug, so that now, as usual, only users with the appropriate permissions for the workflow can edit records.
See also: Workflows in the FM Portal
Bug Fix: API Error Fixed
Due to an error, documents in the portal were no longer accessible via the API. This error has been fixed.
See also: eTASK API
Bug fix: Discrepancy in DIN277 area report resolved
An error has been fixed that caused rooms assigned to a room group to be treated differently in the [Portfolio (BIM) > Property Cadastre > Reports > DIN277-2016 > Buildings] evaluation than rooms that do not belong to a room group.
See also: Room Groups
Bug fix: "Tenant Account Statement" report corrected
The "Tenant Account Statement" report groups the transaction text within a month to display all transactions correctly. This resulted in incorrect calculations when transaction texts were identical. This has been changed so that the transaction ID now forms the basis of the calculation. Identical transaction texts are therefore no longer a problem for this report.
See also: Report: Account Statements per Tenant
Bug fix: Transfer of values from the operating cost statement to the outgoing invoice corrected
Incorrect values were transferred when transferring the operating cost statement to the outgoing invoices. The gross advance payment was entered as a net amount in the invoice line item. This error has been corrected.
See also: Operating Cost Statement
Bug fix: Bank details included in outgoing invoice
When approving a credit note for the tenant, the transfer to the payment order was not executed. Additionally, the entered bank details were no longer included in the invoice after clicking the "Create Invoice" button. This error has been fixed.
See also: Outgoing Invoices
Bug fix: Issue with the Property Explorer resolved
For a short time, errors occurred when opening records from the Property Explorer. We quickly fixed this issue. The Property Explorer is now fully functional again as usual.
See also: The Object Explorer
Bug fix: "Tenant Remaining Lease Term" report corrected
Two companies were displayed in the header of the "Tenant Remaining Lease Term" report. This has been fixed.
See also: Report: Remaining Term of Lease Agreements
Bug Fix: Personalized Views Now Again Support Column Sorting
(Customer Reference: CAFMBT-225)
In your eTASK.FM portal, you can create your own views for tables and other reports and save them for reuse. These views take into account, for example, the showing and hiding of columns as well as the application of specific filters within these columns. For a short time, column filtering was not included in the saved personalized view. We have now resolved this issue, so you can create and use your personalized views as usual again.
See also: Personalized views of tables and reports
Bug Fix: Correction in the assignment of invoices to the next payment run
In isolated cases, invoices were not assigned to the next payment run as planned. This has been corrected: The payment run that occurs immediately before the payment due date is now selected. If no payment run takes place before the payment due date, the payment run occurring immediately after the payment due date is selected.
See also: Payment runs
Bug Fix: The calculation of the next possible notice period for contracts was incorrect
In the lease agreement form, the "Next Possible End Date" field was calculated incorrectly. This has been fixed.
See also: Create Lease Agreements
Bug Fix: Issue with the maintenance plan in dynamic maintenance resolved
Under certain circumstances, after switching to the new, dynamic eTASK.Maintenance, individual orders were no longer displayed in the maintenance plan. We have fixed this issue with this release, so that now, even after switching to dynamic maintenance, all relevant orders are displayed in your maintenance plan.
See also: Report: Maintenance Plan
Bug fix: Improved system message when adding a comment without text input
If a comment is added to a service ticket, it can no longer be submitted if either the subject or the comment text is left blank. Instead of a system error, a human-readable message is now displayed.
See also: Adding comments to records
Bug Fix: Notice periods are calculated correctly
In Contract Management, the next possible termination date was being calculated incorrectly. The calculation has been corrected, and the correct date is now determined.
Bug fix: Notification set up for failed vehicle bookings
(Customer reference: CAFMTT-91)
If two people happen to be looking for the same vehicle at the same time for the same period and book it almost simultaneously, the person who booked later is now correctly notified that the booking was unsuccessful and that the vehicle has since been booked by someone else.
See also: Display Vehicle Booking Calendar
Bug fix: Fixed an error when calling actions
In some forms, an error message occurred when calling actions via the toolbar. We have fixed this issue for you in this release, so you can now use all actions as usual again.
Bug fix: Fixed an error when executing GL_JOB_DELETE_LOGS_SP
(Customer reference: https://jira.swlm.zd.in.bund.de/browse/CAFMTT-56)
An error occurred when executing a procedure in the timer job GL_JOB_DELETE_LOGS_SP. The job could not be completed. This timer job deletes the log data of all timer jobs after a defined retention period. After fixing this error, the logs for the individual timer jobs will again be deleted regularly, along with the login statistics
See also: Timer Jobs
Bug Fix: Operating Cost Settlement Displays the Correct Designation
The term "back payment" was displayed in the operating cost statement, even though it was a credit. The determination of whether the result of the operating cost statement is an additional payment or a refund is now based on the correct value. Depending on the sign of the calculated value, a different term is now displayed in the report. Additional adjustments have also been made to the operating cost statement report.
See also: Report: Operating Cost Statement
Bug Fix: Operating Cost Statement: Tenant Advance Payment Calculated Correctly
An error occurred during the calculation of advance payments when generating the operating cost statement. This error has been fixed.
Bug Fix: Correct Transfer of Postings to Datev
When a payment was assigned to a transfer posting, this posting was transferred to Datev twice. This error has been fixed. The payment assignment of a transfer posting now generates only one journal entry.
Bug fix: Data export to Excel corrected
When exporting from the Crystal Reports "Rent Roll" report to Excel, the total row was misaligned. This has been corrected.
See also: Report: Rent Roll
Bug fix: Error when using bulk update for certain date fields
In some forms, using the bulk update for date fields resulted in the fields being empty. We have fixed this error, so the bulk update is now available to you again as usual.
See also: Bulk Update
Improvement: Improvement in permission assignment
(Customer Reference: CAFMTT-128)
With this release, we have improved the assignment of permissions to menu items. In particular, we have sped up the assignment of permissions to menu items with many sub-items. Previously, errors sometimes occurred there because selecting the menu item took too long. We have now improved this process so that you can use permission assignment quickly and reliably.
See also: Assigning Rights to Menus, Info Areas, and API Paths
Improvement: Expansion of the "SAP Purchasing Group" field in the personnel list
The personnel list includes the "SAP Purchasing Group" field. Here, a person can be assigned to a purchasing group. We have now expanded this field for you so that you can use up to 100 characters there.
Improvement: Ability to enter gender identifiers
(Customer reference: https://jira.swlm.zd.in.bund.de/browse/CAFMLK-8)
Gender can now be selected in the person’s data record. The catalog of available genders can be created and expanded on a customer-specific basis. It is located in [Control Panel \ Basic Data \ Employee Management \ Gender].
See also: Create new users
Improvement: "Master List of People and Rooms" and "Inventory Object List" updated
(Customer reference: CAFMBT-115)
The master list and the inventory object list have been expanded to include additional information about the country and general information about the state, based on the location and building.
Improvement: Description field established for permission groups
Permission groups now have a description field to specify the intended use of the group in more detail.
See also: Create rights groups
Improvement: Communication data now refers to objects
Communication data now refers to objects instead of the outdated "telephone devices" structure. A description has been added to the form. A list of assigned communication data can be displayed on the object.
See also: Elements that can be assigned to a move order
Improvement: Faster search results in lists
With this release, we have improved search performance in large lists for you. Search time has been significantly reduced, so search results are now displayed faster.
See also: Search function
Improvement: "Master List of Contracts" expanded to include location information
(Customer reference: CAFMBT-115)
The "Master List of Contracts" contains comprehensive information about your contracts. Thanks to the filter functions, this master list allows you to create your own reports. We have now expanded the "Master List of Contracts" to include detailed information about the location and the building. If you use the hierarchy options of your eTASK.FM portal to manage your locations, this is also taken into account here.
Improvement: Excel import optimized
(Customer reference: https://jira.swlm.zd.in.bund.de/browse/CAFMTT-52)
The eTASK.FM portal allows data to be imported via Excel for most forms. We have now optimized this import feature for you so that even large amounts of data can be easily imported. Additionally, the Excel import can now be used for even more forms. With this release, for example, you can transfer permission settings to menu items or form sections using the Excel import, as well as dynamic attributes. Furthermore, the Excel import now pays even closer attention to the accuracy and uniqueness of the data being imported. For example, it ensures that data that must be unique cannot be created twice. Thus, employee records that have the same employee ID as an employee record already stored in your eTASK.FM portal cannot be imported.
See also: Importing data using Excel
Improvement: Search speed optimized for tables with large amounts of data
Search speed within tables containing large amounts of data has been improved. Additionally, all search results matching the search term are highlighted in color.
See also: Search function
Improvement: Catalog for federal states and states expanded
The catalog of federal states and the catalog of states have been expanded to include additional columns (such as abbreviations and English names).
Improvement: Manual triggering of a timer job improved
Timer jobs can also be manually triggered outside of their scheduled runs. We have now improved this process. Manual triggering waits for the next "tick" of the timer job, which occurs every 60 seconds. Manual triggers are thus more robust and do not affect subsequent scheduled runs.
See also: Timer Jobs
Improvement: Vehicles and receipts can now be entered in kilowatts
Vehicles and fuel receipts can now also be entered with the correct units (kilowatts for electric vehicles instead of liters). The reports take this into account.
See also: Saving fuel receipts
Improvement: Excel export now available throughout the portal in xlsx format
Previously, there were a few forms in your eTASK.FM portal where data could be exported in xls format. With this release, you can now export your data throughout the entire portal in xlsx format.
See also: Export data to Excel
Improvement: Faster search queries
In your eTASK.FM portal, you can easily search through tables and other reports. We have now improved these search queries, and results are displayed significantly faster. So now you can enjoy an even faster search process in your tables.
See also: Search function
Improvement: Standardization of fields in the hierarchy levels of locations
In hierarchy levels 1, 2, and 3, the code columns are 20 characters or longer, and the descriptions are 100 characters long. The eTASK.FM portal offers you a total of three hierarchy levels to display your locations in a structured manner. For these three levels, we have now standardized the "Code" and "Description" fields so that a detailed and clear overview can be generated. With this release, you can use up to 25 characters in the "Code" field and up to 100 characters in the "Description" field.
See also: Hierarchy in the Property Register
Improvement: New design for the error page in the eTASK Portal
The error page has a new and clearer design that complies with BITV 2.0. Additionally, the display of the data shown there has been revised. Only the data absolutely necessary for error processing is displayed there.
Improvement: Transparent information about system-driven data changes
In your eTASK.FM portal, data records are occasionally modified by the system, for example when using workflows, timer jobs, or other automated features. When a data record is modified by the system, the last user who made a manual change to that record was sometimes listed as the user. We have now made this process more transparent. This makes it immediately clear that the change was made by the system.
Improvement: Direct display of personalized views in the menu
Previously, if you created a personalized view for a list in your eTASK.FM portal that did not yet have a personalized view or filter, you had to clear the server cache before the view could be accessed via the menu. We have now simplified this process for you. Personalized views are now displayed directly without requiring any action on your part.
See also: Personalized views of tables and reports
Support Information: Explanation of Accessibility
In your eTASK.FM portal, this release includes a statement on the status of accessibility according to BITV 2.0 under "System - Accessibility."
Highlight: Logical client management now available
The logical client functionality will be released for the first time in the September 2023 release and further developed thereafter. It is currently in the beta phase. Clients allow you to restrict the visibility of certain data. A logical client is a separate data area within an eTASK system (portal). The business data within a client is protected from access by all other clients. The default client is named "Default Client 01." All data is now available in the default client. By default, client management is always disabled in the portal.
See also: Enable logical client management
Highlight: Excel update function available
In addition to the initial Excel import of data, it is also possible to update existing rows from Excel at a later time. This means you can overwrite existing data. Previously imported rows can thus be filled with new content. Furthermore, it is possible to add new data rows from an Excel spreadsheet to an existing table in the FM Portal. We provide a special import template for this purpose, which is available to administrators in every list. Note: When updating existing data, no business logic checks are performed. This function is intended ONLY for the initial setup of data prior to the actual launch of CAFM (e.g., for migrating inventory data from other systems). It can be used to update existing data records or add additional columns.
See also: Excel Update (Extended Import)
Highlight: New: Dynamic Attributes
eTASK provides static attributes, i.e., a catalog of attributes predefined for customers that cannot be customized. This catalog is ready for immediate use.
In addition, with this release, administrators can create additional attributes and, for example, display and populate them in specific forms. We refer to these attributes as dynamic attributes. They can consist of text, number, and date fields. You can also configure dropdown fields and date fields. You can find detailed information on the procedure in our SupportCenter.
Dynamically created attributes behave exactly like static attributes in the forms. Users can therefore use them as usual. Dynamic attributes are also taken into account during Excel import and export.
See also: Using dynamic fields
eTASK.Key Management
New Feature: Extended Destruction Log
(Customer reference: CAFM.LH.SV.015 | CAFM.LH.SV.024)
When a key is destroyed, you can now specify who performed the destruction and the date on which the key was destroyed. Both pieces of information are also included in the destruction log.
See also: Key Management
New Feature: Extended Loss Log
(Customer reference: CAFM.LH.SV.015 | CAFM.LH.SV.024)
When a key is lost, you can now record which person lost the key and on what date. Additionally, a risk assessment can be recorded. All information is also included in the loss report.
See also: Key Management
New feature: Improved options for organizing key groups into a hierarchy
(Customer Reference: CAFM.LH.SV.015 | CAFM.LH.SV.024)
With this release, key groups can be organized hierarchically by assigning them to a higher-level group. Multiple key groups can also be assigned to the same higher-level key group. This hierarchical structure has no functional impact on your eTASK.FM portal and serves to provide a better overview of your keys.
See also: Key Management
New Feature: Several new options for key management
(Customer Reference: CAFM.LH.SV.015 | CAFM.LH.SV.024)
With this release, we have made several new features available to you regarding your key management. You can now decide whether the note for the key should be displayed in the key log. Additionally, keys can now be issued to departments as well as to individuals. Finally, we have expanded the security areas to include outdoor areas. You can now also assign your outdoor areas to your security areas.
See also: Key Management
Improvement: Standardized reports in key management
(Customer Reference: CAFMBT-282)
eTASK.Key Management offers you a wide range of reports and analyses related to your keys. We have now standardized these and improved their presentation. This gives you an even better overview of your keys.
See also: Analyses in eTASK.Key Management
eTASK.Inventory
Bug Fix: Fixed an issue with Inventory App synchronization
In isolated cases, the connection to the FM Portal would be lost while taking inventory via the Inventory App. If this occurred, synchronization was interrupted. This issue has been resolved.
See also: Taking inventory of objects