...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Release date 1823-03-20232024 |
Changes
Key
Release note
UST-004288
Financials:
When a bank account was specified on the invoice item, this was not taken into account for displaying eligible invoices when trying to add an invoice manually to a collection batch. This is now taken in account.
UST-004771
Integration:
When booking on behalf of someone else in Workplace Experience, the invite for the relevant room should be sent to the person that was booked on behalf of instead of the person that used the app to create the booking.
UST-004886
User Interface:
The search button on search screens only registered a user click when the text was clicked and not on the edges of the search button. This has been fixed so that the entire search button can be used.
UST-004899
User Interface:
Several security related changes were made to mitigate cross-site scripting vulnerabilities.
RFP-002280
User management:
Users with the group 'User management' were unable to archive a user if that user was linked to an external app (used in case of integration with the Workplace App / Workplace experience). This has been solved.
RFP-002339
Checklists:
A workflow function (expired) on the checklist page was not translated into English. This has been fixedKey | Release note |
|---|
UST-004754
Financials:
A meter can now be associated to a list of areas by using an areaset. This can be applied for correctly associating costs to rentable areas within a service charge settlement.
UST-004807
Financials:
Meters can now be added to area sets
UST-003625
Other (Functionals):
The field 'initials' on the object 'Person' had a maximum of 10 characters. This limit has been removed, such that longer initials can also be filled in
UST-004064
Other (Functionals):
The function 'Archive' gave an error if not all mandatory fields on the object that was being archived were filled in. This check has been removed.
UST-004818
Other (Functionals):
It's now possible to define a user interface skin on user level. This used to be only possible on profile level.
UST-004864
Other (Functionals):
In an object selection field (as opposed to a pulldown) it is possible to type a few characters and get suggestions.
The code limits the number of suggestions based on a client value (Client.useAutoCompleteSearchTreshhold). This setting can contain a value between 1 and 50. If this field is left empty, the code defaults to '15'. This has been changed to 50 (The maximum value)
UST-004893
User Interface:
The tabs on instance pages, dashboards and includes have been redesigned so that they follow material design guidelines
RFP-002256
SystemGroups:
Only active system groups are shown in all places where system groups can be found or assigned to users or profiles.
SystemGroups are active based on module settings (E.g. Request related system groups are only active if the request module is enabled)
N.B: Client-specific groups are always active
RFP-001378
Suppliers:
It is now possible to register a deviating postal address for a supplier organization. The postal address is only shown if the supplier has a deviating postal address (This can be indicated on the page of a supplier). This deviating postal address can also be imported via the default import template.
RFP-002346
Reservation settings:
A new setting is added (Approval specific items) to the general reservation settings. Only if this setting is enabled (True) the field on specific reservable objects (Reservable) to enable approval of the item becomes available.
Next to this, group 4. approval reservation items will become active as a mandatory group in all system group overviews.
This setting is automatically enabled for clients that already used this feature (Reservation item approval)
RFP-002297
Reservations:
When creating a reservation, the end time field was not mandatory, even though it is necessary to fill it in in order to get available objects to reserve. This field is now made mandatory (added the *) to make this more clear
RFP-002254
Requests:
When creating a request, the property field is a pulldown type of field. Since this is not very user-friendly if a customer has a lot of properties to choose from it is possible to change this to an object selection screen via a new general setting.
(Request settings tab. Setting: 'Use object selection for properties in request'
RFP-002243
Properties import from O-Prognose:
There is now a default import mapping available for the properties which have been exported from O-Prognose. The property export from O-Prognose can be saved as a .csv file and directly imported into Workplace/Maintenance Management.
This can be used by a consultant if a new Axxerion customer already uses O-Prognose to quickly import all the properties that are already in O-Prognose
RFP-002264
O-Prognose interface:
The setting on a property (ExportToOPrognose) which is used to indicate if a specific property should be interfaced towards O-Prognose was not yet displayed on a property. This field is now added to the process setting tab of a property.
RFP-002267
O-Prognose interface:
If the interface with O-Prognose is active, a new buttonbar is shown on the administrator startboard which has the following buttons:
1: O-Prognose integration information: This will open the documentation related to this integration.
2: O-Prognose reports: This will show all the reports that are used in this integration. These can be used to check which data is available in the integration towards O-Prognose.
3: Properties to O-Prognose: This will show an overview of all properties including the setting (per property) to indicate if the property should be interfaced with O-Prognose
RFP-002018
Masterdata
It is now possible to directly show all results in each of the master data search screens (Organizations, contacts, properties, assets, catalog items) when opening the search screen (instead of having to search first).
Since this is only desirable if the total number of results is limited (e.g. less than a hundred as it would otherwise take (a lot of) time to load while still needing to search) a new general setting is added in which this number should be set (if left empty, no results are directly returned and the user can directly start a search).
N.b: For new clients, this setting is automatically set to 100. It is advised to leave this setting empty if the number of master data objects (for any of the types) is very large.
RFP-002327
End user overviews:
The end-user overviews on the startboard have some additional columns:
My Future reservations now also shows:
-End time of the reservation
-Property of the reservation
-The reservation type
My open requests now also shows:
-Problemtype ('Concerns' field)
-Request type (Wish, complain, etc)
My expected visitors now also shows:
-Expected end time
RFP-002335
Corrective work orders:
The field 'requestor' from the linked request is now also displayed on the corrective work order page.
RFP-002253
Corrective work orders:
The field 'ProblemType' from the linked request is now also displayed on the corrective work order page.
RFP-002225
Corrective work orders:
It is now possible to indicate if a document linked to a corrective work order should be added as an attachment in the work order mail sent to the contractor. This can be done via a new field in the document list (Add as attachment for contractor)
RFP-002148
Corrective work orders:
An include is added where (if found) active contracts are shown which have an active contract item linked to the same asset as the work order.
The user (a service desk employee) will need to have access to view contracts for this include to show results.
RFP-002193
Consultants: Setting up a new client
When setting up a new client, a default e-mail logo (Workplace logo) and announcement is generated in the initialization wizard.
RFP-002252
Areas:
A new category has been added to the area categories: Meeting room
RFP-002330
Administrator: Solution-based rollouts:
User profiles are no longer generated in the solution-based rollouts. Since user profiles are often created apart from activating a new module, this part has been moved to the new user profile dashboard as a stand-alone option.
RFP-001960
Administrator: Solution-based rollout - Maintenance solution:
A solution-based rollout for the Maintenance solution is added. This rollout guides the administrator through the setup of the process, with all process-relevant options and settings directly available from the rollout.
N.B: The Maintenance solution contains multiple modules (Properties, Assets, Request, work orders, contracts) and also the integration with O-Prognose
RFP-002176
Administrator: Solution-based rollout - Energy meters:
A solution-based rollout for Energy meters is added. This rollout guides the administrator through the setup of the process, with all process-relevant options and settings directly available from the rollout.
RFP-002175
Administrator: Solution-based rollout - Cobundu simple ticketing:
A solution-based rollout for Cobundu: Simple ticketing is added. This rollout guides the administrator through the setup of the process, with all process-relevant options and settings directly available from the rollout.
RFP-002173
Administrator: Solution-based rollout - Checklists:
A solution-based rollout for Checklists is added. This rollout guides the administrator through the setup of the process, with all process-relevant options and settings directly available from the rollout.
RFP-002272
Administrator: Settings:
The general settings are split into two parts (Also on the admin startboard and in the navigation menu):
-Client settings (The settings that are not related to specific modules, but general). This option is not available for level 1 admins (See admin levels release note)
-Module settings (All settings related to specific modules, in a tab per module). This option is available for every admin level (however, not every specific setting might be available to level 1 admins)
RFP-002332
Administrator: One startboard
A new startboard is created that contains tabs for every functional profile (E.g. Servicedesk employee, Reservation coordinator, reception employee). Users only see tabs based on the authorizations they are given.
If an admin creates a new user profile, this will automatically get this net starboard. This makes managing user profiles a lot quicker and easier as it is no longer needed to create a specific startboard per (Functional) profile.
N.B: Existing profiles will of course keep their current startboard and using custom startboards will still be available if desired
RFP-002348
Administrator: New user-profile dashboard
A new dashboard is available (which replaces the admin button bar option 'Create user profile) to manage user profiles even better.
This dashboard will show a comprehensive overview of the existing user profiles, an option to quickly create new user profiles, and overviews of system groups that are enabled (based on activated modules) distinguished between optional and not optional groups (Some groups should always be assigned as to not get stuck in a process, other groups are more optional) and already assigned vs not yet assigned groups.
RFP-002255
Administrator: Admin levels:
Until this release, an administrator could enable 'Additional admin options' and based on that setting, have access to customization options. This has been changed to 'Admin levels'. On the user page of administrators, a new field is available: 'Admin level'.
This can be set to the following 3 levels:
-Level 1: Useful for daily admin work (corrections, taking over users, basic module settings)
-Level 2: Admins with level 2 also have access to configuration (enabling new modules, generating user profiles, tenant settings)
-Level 3: Admins with level 3 also have access to customization options (similar to the previous 'Additional admin options'
Level 1 admins cannot see this field and can thus not upgrade their level and can also not take over higher level admins
Each next level always includes the rights of the previous level
All existing admins have been set to level 2 and if 'Additional admin options' was enabled, this is set to level 3
Bugs
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. |