Asset Baseline (26.1)

:arrows_clockwise:1f503🔃#DEEBFF

Release date 07-02-2026

The release notes on this page are relevant to customers on the Asset baseline. For other customers, only a subset of these release notes applies, and this list can be found via: Release Notes Axxerion

Changes

Key

Release note

AXX-6457

Technical update – Internal date/time handling:

We have updated how date and time values are handled internally and stored in the database. This change standardizes date/time processing using modern date/time types and improves consistency and reliability in time-based logic.

This update is not expected to impact customers or existing functionality. However, as date and time handling is often used in custom configurations, customers are encouraged to test date/time–related functionality, for example, in custom scripts and reports that use date/time functions (such as time conversions or period calculations).

No functional changes are required from customers, and existing data remains unaffected.

AXX-6989

Addresses – Timezone field added and page optimization:

The Address page has been updated to include a Timezone field, supporting future logic where the system uses the building address timezone if no object-related regime is set (this is planned for the 26.2 release).

In addition, the Address page has been visually optimized using headers to improve layout, readability, and overall look and feel.

These changes make it easier to manage time zones and enhance usability when viewing or editing address details.

AXX-7084

Administrators – Irrelevant period options removed from import/export connectors:

The period selection fields used to determine the schedule of import and export connectors (for example, weekly execution) have been cleaned up.

Irrelevant options such as Second, Irregular, and Indefinite are no longer shown, ensuring that only valid and meaningful scheduling options are available.

AXX-7410

Administrators – SSO configuration startboard button:

In the previous release, setting up SSO (Single Sign-On) was made available at the client level, instead of requiring root access.
To make this even more user-friendly, when SSO is activated, a new button will appear on the administrator startboard (level 2 & 3 admins): “SSO settings”.

All relevant settings, logs, and potential errors can be accessed via this button. This information was previously only available via Client settings → Authentication tab → SSO operations.

AXX-7319

Administrators – Technical info icon on instance pages

A technical info icon has been added to each instance page and is visible to administrators only.
When clicked, it opens a pop-up displaying technical details of the object, including:

  • Unique reference
  • Database ID
  • Bookmark

This improvement supports debugging and integration-related testing by making key technical identifiers easily accessible.

AXX-6846

Administrators – Validation of client general administrator configuration:

Additional validation has been added for the client general administrator configuration to prevent unexpected issues.
The system now validates whether the client general administrator (as configured in Client settings → Administrator):

  • Is an active user
  • Is a member of the Administrator system group
  • Has at least one system group assigned (without context)
  • Does not have a region assigned
  • Has a full / admin / system administrator user license

When any system administrator logs in, and one or more of these requirements are not met, an alert is shown.

This helps identify configuration issues early and improves reliability for email handling, debugging, and integration-related scenarios.

AXX-7302

Asset App integration – Option to retry sending work orders to Asset App:

An option has been added to retry sending work orders to the Asset App when they were not processed correctly the first time.

On the Technical details tab of a work order, administrators now see a “Resend work order to Asset App” action when the work order has been sent but the dispatch ID (token) is still in Pending status.

Selecting this action triggers the work order to be sent to the Asset App again.

AXX-6048

Asset App integration – Select custom forms per work order:

It is now possible to determine which form to use in the Asset App when assigning a work order to a user.

  • Any form created and published in the Asset App backend is synced to Asset (name and reference only, as it is only used to be able to select the desired form).
  • A new field has been added to work orders (visible when the Asset App is used) that allows selecting the desired form for creating the dispatch in the Asset App.
  • By default, the default form configured in the Asset App external app is used, but additional forms, if created in the Asset App backend, can be selected for work orders requiring specific fields.
  • New or archived forms are synced every 4 hours.

Note: When creating custom forms, follow the guidelines in the Asset App integration configuration guide: https://support.spacewell.com/space/KB/4357490572/Asset+app+integration+module+activation+and+information

This enhancement allows more flexibility in handling work orders by using forms tailored to specific tasks or requirements.

AXX-7231

Assets – Updated asset code logic using Asset code scheme:

  • Asset codes, used to label and group assets, have been extended with support for the new Asset code scheme (AssetTypeSchemeId) field and are now also available outside of Compliance and Maintenance Planning.
  • A new Asset code scheme field has been added to relevant Asset pages and is now also available when Compliance is not applicable.
    Asset code selection supports searching by name and reference and—when an Asset code scheme is set—only asset codes within that scheme are shown.
  • A new Asset code schemes option has been added to the Asset navigation menu, allowing management of asset codes and asset code schemes outside the Compliance navigation options.

All of the above options become available based on a new Asset module setting: “Use asset codes”

Access to the "Asset codes schemes" menu and the ability to edit asset codes and schemes is controlled via the "Edit assets" system group.

This update enables broader and more consistent use of asset codes while avoiding unnecessary menu options for customers who do not require them.

AXX-4266

Customization – Administrator scripts: Convert UTC time to a specified timezone:

Scripts now support converting a date/time to a specific timezone.
This can be achieved using the following script function:

  • toLocal(time, timeZone)

In addition, the .timeZone property is now supported on DateTime variables, allowing scripts to retrieve the timezone associated with a given date/time:

  • timezone = date.timeZone

This enhancement improves accuracy and flexibility when working with time-based custom logic across different locations, such as converting times to building- or office timezones.

AXX-7077

Customization administrators – External references added:

To support advanced customizations and smoother data imports, an external reference field has been added to the following objects:

  • SystemGroup
  • ScheduleItem
  • ReminderSchedule
  • Schedule
  • Regime

AXX-7224

Documents – Configurable file type upload validation:

Support has been added on the Asset Baseline to configure which file types are allowed or rejected when uploading documents.

This option was already available at the root level, but is now visible and configurable on the Asset Baseline. A new client-level setting on the Documents settings tab, allows customers to define which file extensions are explicitly allowed or rejected for uploads.

This feature enhances security by allowing administrators to reject certain file types (e.g., .exe) from being uploaded, in addition to the system’s existing virus scanning of all uploaded documents.

This improvement makes file upload restrictions clearer and easier to manage, supporting security and compliance requirements.

AXX-7309

Long-term maintenance planning – Updated Dutch translation for work activities:

The Dutch translation for Work activities has been updated to “Handelingen”.

This aligns the terminology with Maintenance Planning (O-Prognose) and ensures consistent labeling across the application for the same concepts, improving clarity and usability for Dutch-speaking users.

AXX-6838

Service Desk – Report name enhancements for clarity:

The names of certain reports on the Service Desk Dashboard have been updated to better reflect their actual content and avoid confusion.

Previously, reports such as:

  • “Corrective work orders for me or my team in progress”
  • “Corrective work orders for me or my team not yet forwarded to contractor”

gave the impression that all work orders assigned to team members were included. In reality, users could only see work orders assigned to themselves or work orders assigned to the team but not yet assigned to anyone personally.

To improve clarity, the report names have been updated to clearly indicate the scope of the data, for example:

“Corrective work orders assigned to me or not yet assigned in my team”

This change ensures that users have a correct understanding of which work orders are displayed in each report.

AXX-7068

Translations – Improved handling of underscore-separated translations

The software now provides improved translations for texts consisting of multiple words separated by underscores.

For such texts, the software:

First checks whether a TranslationKey exists for the complete text.
If found, that translation is used. This behavior is unchanged.

If no TranslationKey exists for the complete text, the translation logic has been improved:

  • Previously, the software translated the text word by word: it translated the first word, and then translates the remaining text in the same way.
  • Now, it translates the text by taking the longest matching part from the beginning for which a single TranslationKey exists, and then translates the remaining part.

This results in more accurate, natural translations when multi-word combinations are present.

Example
The text:
error_no_service_type_scheme_found

Previously translated in Dutch as:
”Fout nee service type schema gevonden”

Now translated as:
”Fout geen service type schema gevonden”

AXX-7096

WCAG – Keyboard navigation improvements:

To further comply with the Web Content Accessibility Guidelines (WCAG), keyboard navigation has been improved across the application.

  • The navigation menu supports keyboard interaction. Users can navigate using arrow keys or Tab / Shift + Tab, open items with Enter or Space, and close menu items with Escape.
  • The top left logo is keyboard accessible. When focused, pressing Enter or Space activates it and (re)loads the home screen.
  • The profile menu has full keyboard support, allowing users to navigate to their profile, favorites, and history using only the keyboard.

These improvements enhance accessibility for users who rely on keyboard navigation.

AXX-7148

WCAG – Web Content Accessibility Guidelines improvements:

To further comply with the Web Content Accessibility Guidelines (WCAG), the following changes have been made:

  • Green traffic lights in multiple dashboards and overviews have been updated to dark green to ensure sufficient contrast with the background.
  • In addition to traffic lights (for example, in SLA overviews in Requests and in the Compliance module), a new column has been added next to the traffic lights that displays text indicators (e.g., “On time”, “Not compliant”), making the information accessible to color-blind users.
  • Multiple graphs have been updated to use colors with sufficient contrast against the background.

These improvements enhance accessibility and ensure that key information is perceivable for all users, including those with visual impairments.

AXX-7244

Workplace tickets – Updated notification flow when requesting additional information:

The email notification and user flow for requesting additional information from a requestor on tickets created via Workplace have been updated.

When a service desk agent requests more information on a Workplace-created ticket, the system now sends an email guiding the requestor back to Workplace to provide the requested details.
For customers already using the Request workflow, this specific email must be generated or enabled via the workflow configuration.

This change aligns with the introduction of comment support in Workplace that is planned for the next release (26.2) and ensures a clearer, end-to-end flow for both requestors and service desk agents when requestors exclusively use Workplace.

Bugs

Key

Release note

AXX-6944

Contracts – Index run timeout issue resolved:

The contract index run has been updated to prevent timeouts during large or long-running processes.

Changes include:

  • Only items that have not yet been processed are executed, avoiding unnecessary work.
  • Each item is processed in its own transaction to ensure continuous progress.
  • Index runs are now limited to 30 minutes. If processing is not complete within this time, a message is displayed so the user can continue the run in subsequent batches.

These changes improve reliability and allow large contract sets to be indexed without timing out, while maintaining proper handling of custom fields and apply logic.

AXX-6421

Error when searching for wiki object in wikiId field:

When trying to link a wiki article to a wikiId field (for example, to set a fixed value in this field), an error was shown indicating that the object was not specified.
This issue has been resolved.

AXX-6612

Home icon – Behavior after opening Axxerion via bookmark:

An issue has been fixed where clicking the Home icon after opening Axxerion via a bookmark would incorrectly open an empty object page instead of the home page.

AXX-3014

Reservations – Incorrect cancellation when creating a recurring reservation fixed:

An issue has been resolved where a single reservation could be incorrectly cancelled when it was converted into a recurring reservation.

Previously, when creating a recurring reservation from an existing one, the system attempted to cancel the original reservation without properly verifying whether cancellation was still allowed according to the reservation rules and workflows. In certain scenarios, this could result in reservations being cancelled even though they were no longer permitted to be cancelled (for example due to “reserve in advance” settings or workflow validations).

With this fix, the original reservation is only cancelled if cancellation is explicitly allowed. If cancellation is not permitted, the reservation remains unchanged when a recurring reservation is created.

AXX-6957

Security error when pressing Enter:

In some cases, pressing Enter (for example, to run a filter) would trigger a security error. This issue has been resolved.

AXX-5100

Warning: “Your domain has been blocked for security reasons”:

In some cases, when searching or refreshing a page, a warning stating “Your domain has been blocked for security reasons” was incorrectly shown.
This issue has been resolved.