Skip to content

Release Notes Develop

Features

  • The detail view can now be split across several tabs via tabView. Content (sections, child buckets/tables/charts, documents, map) is automatically distributed to the configured tabs, with badges, dynamic visibility, cross-tab validation and a persisted tab selection per record type. Children assigned to a tab always get the menu, badge count and lazy-loading of a bucket, whether or not bucket is configured for that child.
  • selectFromTree can now be configured as an array of configurations. If more than one configuration is given, the selection dialog shows one tab per configured tree, so values from several different trees can be selected for the same attribute.
  • selectFromTree.filter can now also be configured as an array of filter objects with a per-entry showInSearch flag. Entries with showInSearch: true are added as an initial value of the search attribute, so the user can see and change or remove them. All other filter entries keep the previous, silent background-filter behavior.
  • During schema upload, tree-based role configurations are transformed into permissions (for authz.origin=roles).
  • Tree visibility for V2 and V3 configurations and data requests now uses stored permissions. Unauthorized /userdata and /data2 requests return HTTP 403.
  • The technical user's EAM roles are replicated during role replication.
  • Backend searches using the childNode/ATTRIBUTE format can now also reference a child node in a 1:N relation, not just an inline (1:1) relation. The search runs over the child records, but only the parent record is returned. See Backend search, attribute search fields.
  • A wizard status changedTo transition can now configure menuOnContextRecord, an action menu executed on the direct parent record (e.g. the work order an inspection was started from) after the status was saved successfully.
  • Date and time attributes without an explicitly configured format pattern are now displayed using the locale provided by the user's browser or operating system, consistently in lists, tables, the details view and CSV export. For example, a US-locale user now automatically sees American-style dates (e.g. 9/30/2026) instead of a fixed pattern. Attributes with an explicit format pattern are unaffected and keep overriding the default.

Changelog

  • In the Next Gen apps 36.3+ for iOS and Android, the OIDC login now always starts a new session for every login (as if clearCache were true), so the previous IDP session is no longer reused, unless clearCache is explicitly set to false (see OIDC Overview). This reliably supports the shared-device scenario on iOS, which wasn't possible with the classic apps.

  • An attribute that has no validator of its own, but was marked invalid by another attribute's validation.js (cross-attribute validation), now also blocks saving. Previously such an attribute could be saved despite still being shown as invalid.

  • Loading the side-menu tree now fetches its records without their children (bulk-nochild) instead of with children (bulk). This restores the behavior of the previous client and significantly speeds up the initial tree loading and group expansion for large data sets, especially with small group sizes. The children of a node are still loaded on demand when the node is expanded, so no additional requests are introduced.

  • The new insight-maximo-connector image publishes the versioned Maximo connector and mobile connector archives. See the container image catalog.

Breaking Changes

  • The technical user now needs roles that grant access to the required trees. Check its replicated roles; missing roles cause /userdata and /data2 requests to fail. See Role Replication.
  • The Maximo connector no longer exposes its /auth and /config endpoints. Route configuration requests to the V3 server.

Wildfly 42

  • The shared container runtime now uses WildFly 42 on JDK 25. Custom WildFly-based images, configuration, and deployment overlays must be updated and retested.