March 2021 Release
This release has been approved by eTASK for use in production environments. You can download the release now and install it on your server.
Important Notes
We are discontinuing SQL Server 2014 with this release (March 2021), and starting in August 2021, updaters for the then-current release will no longer install on SQL Server 2014.
Users of the eTASK App for Windows
With the release of this version, an updated version of the eTASK app has been released in the Microsoft Store. Please note that this latest app version is compatible exclusively with the current release version of the portal; that is, both the portal AND all connected mobile devices must be updated.
The current version 2021.1.556.53541 of the eTASK app will be available in the Microsoft Store starting March 13, 2021.
Therefore, please update your mobile devices only if you also plan to update your portal to the latest 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, you must subsequently update your devices to the latest app version as well.
Please make sure to sync your mobile devices before the update.
Service Home Screen with Service Tiles
Improvement: Service tiles can now be used directly as the portal home screen
It is now possible to set up the "MyFM/Order Services" section as a Services tile homepage for users. This allows you to set it as the default page for users. The tiles can then directly display the services offered from the MyFM section. When using the Service Ticket, the ticket category can be selected directly as a tile there.
eTASK.BIM
New feature: Definition of requirements and verification of mandatory documents in BIM models
The BIM profiles and data controlling have been expanded to include verification of required mandatory documents. The BIM profiles are used to define the information requirements for the necessary properties of a component and also form the basis for validating the properties contained in a model via data controlling. Validation takes place when BIM models are imported into the portal or on an ongoing basis for data entered in the portal. This checks whether the information requirements specified for a component in the BIM profile (e.g., does every fire door have the "fire resistance class" property specified) are actually met by the model. Data controlling reports how many components are in the model, how many of them have a value assigned to the attribute, how many do not, and what the resulting "data completeness rate" is. This verifies the model’s data quality according to the BIM profile’s definition.Information requirements may also include the need to store documents associated with a component (e.g., product data sheet, maintenance instructions, etc.). These required documents can now be declared as information requirements for components in the BIM profile alongside the properties, and their completion rate can be monitored in Data Controlling.
Bug Fix: Dynamic Mapping Working Again
During a development update, there was an issue with the dynamic mapping of models. This bug has been fixed, so you can now use dynamic mapping again without any problems.
Bug fix: Document types are now included in the profile
Selected document types added to the profile were not transferred to the profile after saving. This has now been fixed.
Bug fix: Missing components (furniture) are displayed in the 2D view and PDF output
In the 2D view of the BIM Explorer, some components (particularly inventory objects) were not displayed at all or were displayed incompletely. These components were also missing from the PDF output of the 2D view. The 2D view has been revised so that the missing components are now displayed and consequently also appear in the PDF output.
Improvement: The "Profile" web form allows for the selection of mandatory documents
The "Profile" web form has been expanded to include a control display for selecting mandatory documents. This now allows you to select an object when a document type is specified and an object type is selected. This ensures that all necessary documents can be maintained and linked to objects when a building is transferred to the operational phase.
eTASK.MyApp/Inventory
Bug fix: Improved memory usage of our inventory app
Our inventory app now requires less RAM. This allows it to run faster and more stably on your devices.
eTASK.DigitalArchive
Improvement: Inherit documents from the matchcode to objects
Documents can be uploaded directly to the object type, the matchcode, or the object itself, or existing documents can be linked from the digital archive. If a document is uploaded via the matchcode, it can be inherited by all objects assigned to that matchcode. To ensure this, make sure the “inheritable” option is enabled in the document’s settings. This is enabled by default.
You can find the documents inherited via the matchcode in the document upload section of the objects. There, the documents are displayed in the “Linked” column with a document icon in a chain. This indicates that the document has been inherited and therefore cannot be edited on the object.
Improvement: Control for displaying linked documents
The Digital Archive offers improved management of documents assigned to matchcodes/objects. To this end, the CC Editor and the CC Editor’s import function have been updated. Documents are no longer assigned individually to an object; instead, duplicate documents are stored centrally, and the object references the respective document. This significantly reduces the number of documents requiring management.
eTASK.Outlook Room Booking
Improvement: Better performance when opening the Outlook Add-in
Performance when launching the add-in has been improved through optimizations in the room filters. This applies both to launching via "New Meeting" in the Outlook menu and via the appointment entry directly in the calendar.
Improvement: Elimination of portal login when using Autologin and the Outlook Add-in simultaneously
When connecting the portal to O365 with Azure Active Directory and simultaneously using the Outlook Add-in, the previously required additional login by the user in the portal is now no longer necessary. This was previously necessary because, according to Microsoft’s rules, the autologin (SSO) token may only be passed on once—which is already the case for Kerberos authentication. With the now-available authentication via OAuth, however, the valid Azure token is used, which allows for multiple transfers.
Please contact Support if you would like to enable this feature for your portal.
eTASK.Vehicle Booking
Bug Fix: Available vehicles are now displayed directly in the booking screen
In vehicle booking, a filter had to be applied first before the available vehicles were displayed. We have now fixed this; you can see all available vehicles directly in the booking screen without using a filter.
Improvement: Vehicle Booking "Starting Point" Location Selection: Only Locations with Bookable Vehicles Are Available
Vehicle booking has been optimized so that only locations where bookable vehicles are actually stored in fleet management are offered as the "Starting Point."
eTASK.Operating Cost Settlement
Improvement: Direct costs of a tenant can now be added to the operating cost statement
When adding a tenant’s direct costs, these did not appear on the operating cost statement. This has now been fixed: A tenant’s direct costs can be added to the statement.
eTASK.Cost Entry
Bug fix: The entry form for incoming invoices is now displayed correctly in all browsers
The entry form for new incoming invoices was not displaying correctly in all browsers we support. This has now been fixed; you can once again view the entire entry form in all browsers.
Bug fix: Line items on an outgoing invoice are displayed in the defined order
In outgoing invoices, the sorting of items in the print documents was based on the order of entry. This has now been fixed: On outgoing invoices, partial services appear according to the defined numbering.
Bug fix: The "Financial Accounting Export Date" is set only for posted invoices
Under certain conditions, incoming and outgoing invoices were assigned a "Financial Accounting Export Date" even though these invoices had not yet been posted. The issue has been resolved.
eTASK.Open Spaces
New Feature: New module for managing "Real Estate"
In the new "Real Estate" section, you can manage the ownership and collateralization of your properties. The feature offers expanded data structures where information from land registry departments, regarding loans, land charges, etc., can be managed.
eTASK.Service Ticket
New feature: Offer service categories selectively in buildings
The Service Ticket now allows you to specify that certain service categories are not offered in individual buildings. If these buildings are selected in the Service Ticket when using a specific category, the user receives a notification that the desired service is not available in the selected building. For example, if a cleaning service is generally offered but not in a specific building, a notification appears when the "Cleaning Service" category is selected in that building.
eTASK.Room Reservation
New Feature: API Service for Confirming Room Reservations Created
The eTASK API has been expanded to include a new function for confirming room reservations. This function can be used to require that booked room reservations be confirmed on-site at the room—e.g., via a touchscreen—within a defined time period before and/or after the start of the reservation. If this is not done, the room is released for booking again.
Bug Fix: Catering Receipt Includes Elements for Which This Feature Is Enabled
In some catering receipts, too many items were displayed. Now, only the items for which the creation of a catering receipt has been enabled are displayed.
eTASK.FM Portal
New feature: Login to the portal via various login providers
The eTASK FM portal now offers its users various cross-platform login options. Use your existing Google or BIMSWARM login credentials to sign in to the FM Portal. Users can also authenticate for the FM Portal via Microsoft Azure Active Directory (Azure AD) or OAuth 2.0. These authorization protocols provide users with a high level of security for the data required for login.
Improvement: Length limit for IFC_CLASSIFICATION_REFERENCE_BEZEICHNUNG increased
Longer entries in the IFC_CLASSIFICATION_REFERENCE_BEZEICHNUNG column for objects in our portal were frequently truncated. This column now allows longer strings of up to 100 characters. Terms entered up to this character limit are displayed in full.
Improvement: Uniform “technical property/building number” available in the CAFM cross-section service
The location code has been extended to 14 characters. This allows for the representation of longer location identifiers.
Improvement: Integration of SAML for user login
By integrating SAML (Security Assertion Markup Language) as an authentication and authorization protocol into its IT products, eTASK now offers its customers faster user login via Single Sign-On.Each user’s access request is transmitted in XML format to the FM portal via a central user database, supplemented by a digital signature, where access is granted after successful verification. Through the central management of user data and rights, eTASK software products offer enhanced IT security.
Improvement: Automatically assign matching matchcodes to imported objects
Objects of a specific object type can now be automatically identified based on the individual attribute values of a matchcode and assigned to that matchcode. The assignment is performed in the matchcode using the function “Extras - Search for Objects by Attributes & Assign Matchcode.” When this function is activated, the system searches for objects whose individual attribute values match those of the matchcode. If this is the case, the objects are automatically assigned to the matchcode. This function helps structure imported object data (e.g., from Excel lists, third-party systems, or BIM models) and easily assign appropriate matchcodes to the objects.
Improvement: Adjustment of the Setup.log
The setup previously recorded passwords in the log file. This has been changed: The log file no longer contains any password entries.
Improvement: Date columns in lists reduced
The display area required for a date column in a list view has been reduced. This makes the display in the portal clearer.
Support Information: Change to eTASK System Requirements Effective August 2021
With the current release (March 2021), eTASK is discontinuing support for SQL Server 2014. This means that starting in August 2021, future updates to the then-current release will no longer be installable with SQL Server 2014.