Core Engine Release 6.1

July 2026

We upgraded! What's new? Learn more about new features, technical changes and solved bugs in 4App Core Engine.

Note on upgrading: If you skip a version when upgrading, check all release and patch notes in between for important information. They apply cumulative.
Note on individualization: If your 4ALLPORTAL is highly customized or if you installed individual apps, please contact your implementation partner before upgrading. We recommend checking your custom contents, especially layouts and object renderers, carefully after an upgrade.

Improvements

Confirmation Dialog Before Resetting Changes

Clicking the "Reset" button in any view, for example, during a mass change, now opens a confirmation popup. Values will only reset after you confirm them explicitly. This prevents accidental data loss when "Save" and "Reset" are close together.

Widgets Keep their State when Navigating Back

Widgets now remember their scroll position and pagination (e.g., number of records shown) when you navigate into a record and return to the list — so you no longer lose your place.

Technical Changes & Admin Instructions

Configurable HTTP Client Timeouts

The connect and read timeouts of the outgoing HTTP clients (used for license validation, the JWKS renewal, feature flags and related calls) are no longer hardcoded and can now be configured via the environment variables SPRING_HTTP_CLIENTS_CONNECT_TIMEOUT and SPRING_HTTP_CLIENTS_READ_TIMEOUT (e.g. 5s, 2m).
Deprecation: The property prefix changed from spring.http.client.* (singular) to spring.http.clients.* (plural), in line with Spring Boot 4. The old spring.http.client.connect-timeout and spring.http.client.read-timeout keys (env vars SPRING_HTTP_CLIENT_CONNECT_TIMEOUT or SPRING_HTTP_CLIENT_READ_TIMEOUT) are deprecated and no longer honored.
What to do: Update any external overrides to the new spring.http.clients.* form.

New Gauge Metric for Total Number of Active Users

The new gauge metric 4allportal_core_user_total reports the number of active users (not deleted, not disabled) per license type (default, consumer, share). The metric is collected once after engine startup and then on a daily schedule. The schedule can be configured via the cron expression FOURALLPORTAL_USER_COUNT_CRON (default: 0 0 0 * * *, UTC).

Template Engine Support for Feature Flags

A new template engine function, hasFeatureFlag, is available for evaluating feature flags, e.g. in metadata renderer configurations. It returns true when the specified feature flag is enabled and active, and false otherwise, including for unknown flags. The function can thus be used to control the visibility of fields or sections.
This change is backward compatible and does not affect existing configurations unless the new function is used.

Solved Bugs

• Fix PID trees that could fail to save user assignments with inherited permissions after a database lock timeout
• Fix the conversion of TIFF images with an alpha channel, which could previously render with incorrect transparency
• Fix the <type> of a group renderer to match case-insensitively, so that values like Flat or Foldable work the same as their lowercase forms
• Fix generic creation error message that was displayed even when more detailed information was available

Patch releases

Version 6.1.1

• Fix unexpected error messages when a tooltip should be shown