Asset Baseline (26.5)

General – Product name updated to Asset in the browser title: 

The product name "Axxerion" has been replaced with "Asset" in the browser title, which is shown in the browser tab and title bar, and in the other places in the interface where it was still visible. This continues the product naming alignment from earlier releases. 

Note: For now, URLs that contain "Axxerion" stay the same.

Reservations – Introducing service points: 

As of this release, service points can be used in Workplace and configured in Asset. A service point is the place that provides a service, such as a restaurant, a pickup point or a delivery provider. Each reservable service, such as catering or other services, can be linked to one service point. 

Service points make it possible to: 

• Filter available services by service point when creating a reservation in Workplace. 
• Prevent a reservation from combining services from different service points, so users aren't expected to be in two places at the same time. If a user tries to add a service from a different service point, an error is shown. 

Service points can be enabled with the new 'Use service points' setting in the reservation module settings. Once this setting is enabled: 

• A new 'Service points' option is available in the Reservations navigation menu, where administrators and reservation coordinators can create and manage service points. 
• A 'Service points' tab is available on buildings, sites and regions, under the related objects menu. It shows the service points for that building, and new service points can be created there directly. 
• A 'Service point' field is available on reservable services. Only service points for the same building, a parent building, or with no building set can be selected. 
• The catering and services overview on the reservation coordinator startboard tab can be filtered by service point. 

For more information, see the Service points section in the reservation module article in the Knowledge Base, which will be available once this feature is released.

Reservations – Delivery location now shown for services and equipment: 

As of this release, a delivery location for catering, services and equipment can be set when making a reservation in Workplace. This is especially useful for reservations without a room, where it wasn't previously clear where items had to be delivered. 

In Asset, the delivery location is shown as a read-only Services delivery location field on the reservation page. The field only appears when a delivery location has been set. 

The delivery location has also been added as a column to the Overview catering/services and Overview assets/equipment reports on the reservation coordinator startboard tab.

Reservations – Services and equipment can now be added to reservations created via an external calendar: 

You can now add services and equipment, such as catering, to reservations created via an external calendar (e.g. Outlook), in both Asset and Workplace. This works for single and recurring reservations. Previously, these reservations couldn't be changed in Asset or Workplace. 

Reservation details that come from the external calendar, such as the subject, start and end time, and the reserved rooms, stay read-only in Asset and Workplace. These details can only be changed in the external calendar. 

Changes and cancellations made in the external calendar can't be blocked by Asset. If a reservation with services or equipment is changed or cancelled in the external calendar after the allowed change or cancellation period, the change is still applied, but the reservation is flagged as a late change or late cancellation. The existing overview of late cancelled reservations now also shows these late changes and cancellations, so administrators and reservation coordinators can follow up where needed.

Reservations – Notice added to the reservation change email for reservations created via an external calendar: 

Services and equipment can now be added in Asset or Workplace to reservations created via an external calendar (e.g. Outlook). If such a reservation is then changed again in the external calendar, the change can conflict with the services or equipment that were added. For example, equipment may already be reserved at the new time, or a service may not be available in the new building if the location was changed. These changes can't be prevented when they're made in the external calendar. 

To make users aware of this, the "Your reservation has been changed" email now includes a notice about these possible conflicts. The notice is only shown for changed reservations that were created via an external calendar and include services or equipment.

Requests – Building selected first and service types based on the building: 

When creating a request, the building is now selected first, and the service types offered depend on the selected building. This supports location-based service type schemes and aligns Asset with other Spacewell products, such as Workplace, Space Management and Maintenance Planning, which are also building-based. 

The following changes have been made: 

• Building comes first: When creating a request directly in Asset, the Building field is now the first field under the "Request data" heading, above the service type. 
• Service types based on the building: A service type scheme can now be set on the Process settings tab of a building, site or region. When a building is selected on a request, the service types offered come from the scheme on that building or its parent site or region. If no scheme is set there, the default service type scheme is used, as before. 
• New default service type scheme setting: A new default service type setting has been added to the Requests module settings. When a request is created, the service type scheme is set based on the service type scheme linked to the location first, then the default service type scheme, and if there is no default service type scheme specified, the standard Asset Baseline default service type scheme. 
• Also applied in Workplace: Workplace now also uses the selected location to determine which service types are available when creating a request, based on the same service type scheme logic in Asset. 
• Service type page shows its scheme: The service type page now shows which service type scheme the service type belongs to. 
• Building field always visible: The service type no longer determines whether the Building field is shown. The service type can still make the field required. On service types, the "Not visible" option for the Building field has been renamed to "Not visible (Obsolete)" and no longer has any effect. In a future release, this setting will be replaced by a yes/no toggle that only determines whether the Building field is required. 
• "Use buildings" setting obsolete: The "Use buildings" setting in the Requests module settings no longer controls whether the Building field is shown on requests or whether building details are hidden in service desk overviews. 

Note: For service types that were set to hide the Building field, the field is now shown, but not required. On all other requests, the only visible change is that the Building field now appears at the top instead of below the description.

Integrations – Option to automatically link new service types to the Workplace API connector: 

A new setting has been added to the Workplace integration settings that automatically links newly created service types to the Workplace API connector. This works the same way as the existing settings for other objects, such as buildings, areas and system users, so new service types no longer need to be linked manually. 

By default, this setting is disabled.

Integrations – More checks added to the calendar integration debugging overview: 

The debugging overview for the calendar integration API connector now includes more checks. These help administrators and consultants find configuration issues that can cause synchronisation problems with an external calendar (e.g. Outlook). This makes setting up and troubleshooting the calendar integration easier. 

The overview now also shows, for example: 

• Whether reservations are enabled and conflicting reservations are disabled. 
• Areas linked to the API connector that aren't reservable. 
• Reservable rooms linked to the API connector that use regimes or blocked dates.

Buildings – Access restrictions now inherited from parent buildings: 

Access restrictions on buildings are now inherited by their child buildings. If a user doesn't have access to a parent building, such as a site or region, they will also no longer have access to the buildings below it. Previously, users could still access these child buildings, because the restriction wasn't inherited. 

This change makes access restrictions for locations work as expected and better aligns Asset with other Spacewell products, such as Workplace. 

Note: This change may affect existing setups where users don't have access to a parent building, intentionally or not, but do have access to its child buildings. After this release, these users will lose access to those child buildings. We recommend that administrators check their access settings and update them where needed.

AXX-9379

User interface – Small visual refinements to the login screen, toggles and sorting icons: 

Following the design updates in the previous release, a few small visual refinements have been made to bring these parts of the interface fully in line with the Spacewell design system: 

• Login screen: Minor layout and styling tweaks. 
• Yes/no toggles: Disabled toggles now use the correct, lighter appearance. 
• Column sorting icons: The sorting icons are now more compact, with more space between the column title and the icon.

User interface – Keyboard navigation support added for the info bar and background task list: 

To further comply with the Web Content Accessibility Guidelines (WCAG), keyboard navigation support has been added for the info bar and the background task list. With the keyboard, you can now open the background task list, open a task and view its results.

User interface – Welcome message on the login screen now translated: 

We resolved an issue where the "Welcome to Asset" message on the login screen was always shown in English, even if the browser was set to another language, such as Dutch. The message is now shown in the browser's language.

Technical update – Hostname verification for outgoing web services: 

Outgoing web service connections now verify that the certificate of the receiving server matches its hostname. This improves security for outgoing integrations, especially those using mutual TLS (mTLS), by protecting against intercepted or manipulated connections. As part of this change, the underlying connection library has been upgraded to a modern version. 

This change isn't expected to affect correctly configured integrations. However, outgoing web service calls to servers with an invalid or mismatched certificate will now be rejected. We recommend testing your outgoing web service integrations after this release.

Customization administrators – External reference field added to price indexes: 

An external reference field has been added to price indexes. This field can be used as a key value when importing price indexes or for linking them to external systems.

Customization administrators – Configurable fallback language for translations: 

A Fallback language field has been added to languages. When a translation is missing in a custom language, the translation from its fallback language is now used, instead of always falling back to English. 

For example, a Flemish language can be set up with Dutch as its fallback. Only the Flemish-specific translations need to be added, and Dutch is used for everything else. Translations added to Dutch later are also shown automatically to users who use Flemish. This avoids copying existing translations when creating a closely related language.

Administrators – Deleted parent objects with active child objects moved to the archive: 

Deleted parent objects (objects in the bin) that still have active child objects (not in the bin) have been moved to the archive, together with their child objects. This applies to buildings, areas, project phases, budget items, cost centers, assets, bank transactions and distribution keys. 

In the past, deleting some objects didn't automatically move their child objects to the bin as well. As of 1 January 2027, objects in the bin will be permanently deleted again after 90 days, unless a different period is set for the object. Without this change, permanently deleting a parent object could also delete its active child objects. 

As a result of this change, some child objects may no longer appear in the application, because they have been moved to the archive. Objects in the archive are never permanently deleted, so this is a safeguard against unintended permanent deletion. Archived objects can be restored from the archive if needed.

Reservations – Filtering on a building in the reservable objects overview resolved: 

We resolved an issue where you couldn't set a building when filtering in the reservable objects overview. When using the three-dot icon next to the building field, the buildings in the results couldn't be selected. Buildings can now be selected as expected.

Reservations – Incorrect time in reserve from/until error message resolved: 

We resolved an issue where the error message shown when adding catering or services outside the configured reserve from/until period displayed the wrong time. The time was shown in UTC instead of the time configured in the settings, for example 12:30 instead of 14:30. The check itself worked correctly. The error message now shows the configured time.

Contracts – Automatic contract period extension resolved: 

We resolved an issue where the automatic extension of contract periods could fail to set the correct end date for contracts with multiple contract period schemes. The contract period end date is now extended correctly, in line with the configured contract period schemes.

User interface – Page layout issue with maintenance messages resolved: 

We resolved an issue where showing a scheduled maintenance message could break the page layout. This made columns too narrow and left some text, such as field descriptions, unreadable. Pages now display correctly while a maintenance message is shown.

User interface – Hiding columns after changing the column order resolved: 

We resolved an issue where hiding columns with the column editor could hide the wrong column if columns had been moved first. Hiding columns now works correctly after the column order has been changed.

User interface – Application sometimes not loading resolved: 

We resolved an issue where the user interface sometimes failed to load or stopped working. This happened at random moments on different environments. In most cases a page refresh fixed it, but sometimes the server had to be restarted.

Customization administrators – Script editor scrolling and text selection issues resolved: 

We resolved several issues in the new script editor that affected scrolling and text selection: 

• The highlight on the active line stayed in a fixed position on the screen when scrolling, instead of moving with the text line. 
• Double-clicking a word could make the editor scroll and select different text than intended. 
• Selecting text by dragging with the mouse could make the editor scroll unexpectedly and select more text than intended. 

The script editor now scrolls and selects text as expected.

Administrators – Duplicate runs of import and export connectors prevented: 

We resolved an issue where an import or export connector could run more than once at the same time. Editing a connector while it was running, for example on the connector page, could start a second run right away, which could create duplicate records during imports. 

A connector that is already running is no longer started again until the current run is finished.