Workplace Management (24.2)
- Gilles Ghyssaert
- Bobby van ter Beek
Release date 23-03-2024
Changes
Key | Release note |
|---|---|
Admin navigation menu and startboard A few small updates have been done in the 'Admin' navigation menu and the administrators startboard: 1: The ‘Groups' search was a report (filter screen with the results in the next page). This has been replaced by a ‘keyword search' with the results directly shown below. This makes it possible to search on multiple fields (via keywords) just like for most of the other objects (Assets, Requests, Reservations, etc). 2: The ‘Authorize users’ navigation menu option is replaced by the ‘User profile dashboard’. This dashboard was already available on the administrators startboard and has been the up-to-date way to manage and assign profiles to users. | |
Module activation for exchange A new 'Module activation' has been added for the Microsoft Exchange (Outlook reservations) integration. Via this module activation, the external app that is used to set up the integration on the Workplace Management side is generated. This module activation will guide the user through (parts of) the setup for this integration and also contains a direct link to the complete documentation for setting up this integration on Knowledge base. | |
New 'module settings' tab for User management A new module settings tab has been added: 'Users'. This tab (found under the 'Masterdata' header) is always available and shows the relevant settings for users. Previously, these settings were found on some of the client setting tabs (interface and authentication), they have been removed there and added together in this new tab. | |
SystemUser now has a unique identifier The object 'SystemUser' now has a new field 'uniqueReference'. This will automatically be populated with a unique reference and can thus be used as a unique identifier of a system user. | |
Assets overview per property The 'related assets' overview in a property now also directly shows the results based on the general master data setting 'Show master data objects directly if less than X'. Next to that, this overview now has the same columns as the regular asset overview (when searching assets directly via the navigation menu). | |
Compliance: Recent updates to the legislation If the Compliance module is used and the user has access to the default legislation, recent updates to the legislation are now shown directly on the startboard of the user (instead of only on the Compliance dashboard). | |
Compliance: NL/SfB-code on asset It was already possible to link a code (for the Dutch legislation, the NL/SfB code) to an asset related to compliance. But this field was only visible on the 'Compliance' tab. The code field is now added to the general page of an Asset and the label of the field is changed to 'NL/SfB-code' in Dutch. This field is only shown if compliance applies to the asset. | |
Compliance: Legislation document applicable by default When generating new legislation documents (for instance, when linking a legislation to an asset), each legislation document is now applicable by default. Previously these were not applicable by default. | |
Compliance: Link multiple assets to a legislation From now on, it is possible to link a specific legislation to multiple assets in one action, instead of always doing this per asset via the asset page. This can be done on the legislation, which contains an extra 'include' that shows the assets linked to this legislation, including an 'Assign assets' button, to add more assets in one go. | |
Compliance: Asset overview updates The compliance asset overview has been updated to also include columns regarding the related area and assigned legislation(s). | |
Compliance: Addtional filter options When searching for a legislation to link to a building, an additional filter is added, in which the user can filter between legislations only related to buildings or related to buildings and assets. | |
Admin Customization: Filter on enumeration items From now on, it is possible to filter enumeration items on a page field linked to an enumeration field. This can for instance be used to only show a sub-set of request statussen in the request filter page. An example script for the RequestStatusCode field: result = [] ; | |
Long-term maintenance work order activity overview in work order When assigning work activities to a work order, the name of the work activity was not shown in this overview. This has been added. Next to that, in the list of assigned work activities to the work order, the related asset was not shown, this has also been added. | |
QR codes on Areas are now always unique: It was already possible to generate a QR code for areas (which are used in the integration with Workplace Experience, for the scan-to-book feature), however, the QR codes were generated based on the reference of the Area. Since the reference is also editable and often used by a customer to fill in the room numbers, these references might not be unique over multiple buildings. Since the QR codes should be unique, the QR codes are now generated based on the unique reference field. If generating QR codes for areas is already enabled, the setting (Module settings -> Masterdata tab -> Properties and areas -> Automatically generate QR code for areas) should be switched off and on again. This will make sure all new areas or areas without a QR code will get the QR code based on this unique reference (areas that already have a QR code will not be updated). | |
Reservations navigation menu search screen: The 'Reservations' navigation menu option directly loaded and showed all the reservations taking place today. Especially for customers creating a lot of reservations, this is taking too much time to load, might lead to too many results to display, and is not relevant anyway (the user just wants to search based on keywords). To have more control over the default behavior of this screen, a new general setting is added (Module settings -> Reservations tab -> 'Initially show reservations in searchpage') in which the initial loading behavior can be selected: -Reservations taking place today (default behavior, also if this setting is left empty) | |
Maximun number of reservations from recurring reservation The maximum number of reservation instances generated from a recurring reservation has now been fixed to 1080 reservations (equal to the maximum in Outlook). Before, it used to be dependent on several different system settings. it is still possible to lower this number on the general client level via the reservation settings page, field 'Maximum scheduled occurrences'. | |
Check on reserved objects when changing a reservation: When submitting a new reservation, a check is done if the reservation contains at least one item to reserve. This check is now also added when changing and resubmitting an existing reservation, to avoid users from unintentionally submitting reservations without actually reserving anything. | |
Start in a different startboard tab: When using the default Workplace Management startboard, key users have multiple tabs on this startboard (e.g. the general tab for creating reservations and requests and a service desk tab to handle requests as a service desk employee), from now on, a user can set the default startboard start tab on its user settings page. Via this new setting, the user will always start in that tab (when logging in or clicking on the logo in the top left corner to return to the startboard). This will make sure users can decide by themselves in which of the multiple tabs available to them, they always want to start. This option is only available to users that have multiple startboard tabs available. | |
User management: Warning when removing all system groups A warning is added when all the system groups are removed from a user that is still active. A user that has no direct system groups linked to it, will not be able to use the system. The warning is added to inform user managers about this potential issue directly. | |
User management: Non-partner user can no longer change partner users To avoid customers from changing users that are used by Spacewell support or implementation consultants, a non-partner user can no longer change the user settings of a partner user (This is only related to fields on the Systemuser object, not the related contact). | |
User management: Non-admin users can no longer change admin users To avoid user managers who do not have administrator access themselves, from changing users that have administrator access (Potentially resulting in not having any administrators and needing support to restore this), non-admin users can no longer change the user settings of a user with administrator access (This is only related to fields on the Systemuser object, not the related contact). | |
User management: No londer possible to change the 'Administrator' user licence To avoid users from changing user licenses for users related to Support/Spacewell consultants and technical users related to API integrations, the user license on the SystemUser page is read-only if it has the value Administrator, and this list also does not contain the value Administrator. If any changes to the licenses are needed for these users, these will need to be requested via support (who can change these values). | |
Users management: User settings tab optimized The 'Settings' tab on the user page has been optimized. It contained some irrelevant or obsolete settings, which have been removed, and (hover-over) help texts and some label improvements for the relevant fields are added. | |
Users management: User type renamed to User licenses To be more clear and consistent, the field in which the license (e.g. full user, limited user) of the user is defined, is renamed from 'User type' to 'User licenses'. | |
Visitor workflow update The expected arrival and departure times of a registered visitor could be changed without changing the status of the visitor. Not changing the status of the visitor workflow means it is impossible to send a new e-email or trigger a possible (custom) update to another system (e.g. badge access system). Because of this, the visitor workflow has been updated. | |
Work order status name update The work order workflows (Corrective, Preventive, and LTMP) contained two statuses with the same name: 'Rejected'. This has been updated to be more clear and distinctive: | |
Work orders: New general setting for planned vs. actual amount When using work order items, by default the planned amount of the items was copied to the actual amount when approving the work order. Even though the user could still change the actual amount, it is not always desired to copy it, therefore a general setting is added (Module settings -> General work order settings tab) in which it can be indicated if the planned amount should be copied to the actual amount. | |
Workplace Experience integration: Update to show linked objects The external app (used to set up the integration between Workplace Management and Workplace Experience) is used to view the objects related to the integration (Properties, Areas, and System users) directly in the page includes without a filter option. Since this would lead to errors for customers with more than 1000 objects, these page includes are now updated to Searchviews (A keyword search option with the results directly underneath it) that initially show the first 10 results (using the search will return all the result based on the keywords). | |
| Module settings for reservations optimized The Module settings tab for reservations has been optimized. It contained some irrelevant or obsolete settings, which have been removed, and some label improvements for the relevant fields are added. next to that some headings are changed. |
Bugs
Key | Release note |
|---|---|
Purchase orders e-mail contained HTML tags Some of the e-mails in the Purchase order process contained HTML tags ("<br>"). This has been fixed. | |
Setup and tidy up settings on reservable objects When using the 'Setup' or 'Tidy up' time fields on a reservable object (which can be used to add additional time before or after a reservation on the object, to reserve time for setting it up or cleaning it), decimals (e.g. 1,5 hours) were not correctly supported and it was always rounded down when automatically blocking the period before or after the reservation. This has been fixed. | |
Next reservation on reservable object Reservable objects (e.g. an area) showed the next reservation (reservable field 'next reservation'), this did not work anymore and has been fixed. When a new reservation is created for an object, this field is correctly updated again. | |
Trust relation bug fix When generating a shared key (AES) for a trust relation by using Axxerion script, the generated key was incorrectly formatted which prevented the user to make use of it. This has been fixed, the correct formatting is now applied. | |
Unsupported characters bug fix When updating data in text fields via a planning script (for instance via an API) that contains unsupported characters (For instance, certain smileys that are not supported in our current Unicode version), an error was thrown and the script was deactivated. This has been updated, such that the unsupported characters are skipped and the script continues without an error. |