Release 5.1.0

This release is available since December 2, 2025.

New features

Note: Most new features will only become available in the Modeler with the next release in February 2026.

  • Numeric fields can now be rendered as actual numeric inputs. This introduces new settings such as min, max, and step. More information on numeric inputs: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input/number

  • Browser autocomplete is now enabled for additional input types:

    • Date

    • Duration

    • Number

  • Entity reference fields can now be displayed as comboboxes.

  • Added support for querying all rows in a nested list, instead of only rows related to the current parent. This applies to:

    • Datagrid and repeater UI components

    • Data export (CSV, Excel, JSON, XML)

    • Loop and list flowchart nodes

  • The image UI component can now have a title attribute in addition to alt. Labels rendered as images can also include both attributes. More info: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/img#alt https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/title

  • The data export flowchart node now supports skip and take (paging).

  • Labels containing an entity reference can now evaluate the entity’s default label expression.

  • New WEM expression functions added: GetFlowchartId(), GetFlowchartName(), GetNodeName()

  • Added the order by keyword to WEM expressions, useful especially for loop statements in widgets or script blocks.

  • Added the SHA512() WEM expression function.

  • Added the IsDirty() WEM expression function to check whether a row or field has unsaved changes.

  • WEM OAuth now supports RSA SHA512 for JWT signatures.

  • You can now explicitly configure an application binding to request a client X.509 certificate during the TLS handshake. Previously, this behaviour depended on the hostname containing "webservice".

Bug fixes and improvements

  • Fixed an issue where a widget script using navigate to @NavigationItem would error if the item was undefined. It now silently ignores the instruction, consistent with follow @Exit and execute @Flowchart.

  • Extended the supported date range of FromUnixTimestamp() to correctly handle dates past the year 2038.

  • Fixed validation issues when using the “Navigate To” and “Clear Session” flowchart nodes.

  • Fixed an issue that occurred when storing empty temporary files.

  • Resolved a WEM debugger issue where certain breakpoints resulted in an error page.

  • It is now possible to define a custom HTTP endpoint at the root path / of an application.

  • Improved the mechanism for requesting Let’s Encrypt certificates.

  • Fixed an issue where checking the status of a non-existent async task returned queued instead of not found.

  • Fixed an issue where comet listeners could not start from pages with nested URL paths.

  • Various small improvements and fixes to the runtime API used by the WEM DevOps portal.

  • Fixed an issue where FileUrl() added a double slash (//) when the hostname was included.

  • The WEM HTTP request node now accepts any Authorization header value, even if not strictly compliant with HTTP spec (e.g., missing a formal authentication scheme).

  • Fixed a bug in design templates where the WEM button bar was added twice.

  • Restored the behavior where autocomplete suggestions appear immediately when minimum characters is set to zero.​

  • Fixed an issue with the positioning of the datetime picker.

Configuration changes

  • The nginx service has been changed from a DaemonSet to a Deployment with 2 replicas by default. It will therefore no longer run on every node automatically.

  • Helm chart indentation has been standardized to 2 spaces.

  • Added support for configuring topologySpreadConstraints and affinity for:

    • applicationService

    • applicationServiceTasks

    • documentCreator

    • nginx

  • Removed the option to configure the number of replicas for the configServer.

  • Removed optional sections related to the migration from version 4.1.

  • Reduced default CPU request for loggingService from 400m → 100m.

  • Reduced default CPU request for portalrepository from 400m → 100m.

  • Outlook message files uploaded at runtime are now correctly recognized and will be downloaded using the .msg extension.

Impact analysis

  • You must update to 5.0.x before upgrading to 5.1.

  • Expect a brief downtime (a few minutes at most) during the upgrade.

  • Runtime database schemas will be updated. Rolling back to 5.0 requires manually reverting these schema changes.

  • Applications published to a 5.1 runtime cannot be deployed to a 5.0 runtime.

Runtime database schema changes

The following Postgres runtime schemas are updated:

  • AiAgentHub: 1.0.2 → 1.0.3

    • Added column tblAiAgentFile.FileSourceId

  • Log: 1.0.0 → 1.0.1

    • Added column tblScheduledTaskLog.ExecutionId

  • ApplicationConfig: 1.0.11 → 1.0.12

    • Added column tblBinding.RequestClientCertificate

Last updated

Was this helpful?