Core Engine Release 4.49

December 2025

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.

Technical Changes & Admin Instructions

App Management: Automated Update Label

In the App Management snap-in, all managed 4Apps are now labeled "Automated update". They can no longer be updated or deactivated. This applies to all 4Apps that are listed in the APPS_INSTALL environment variable in your docker-compose file.
Please note: The Core Engine is always treated as a managed 4App.

API: New Open API Endpoint for Prometheus Metrics

We have added a new Open API endpoint for retrieving Prometheus metrics. The GET /api/system/prometheus endpoint provides metrics that are compatible with Prometheus monitoring systems. This allows administrators to track system performance, request rates, and resource usage directly via the API.
The endpoint supports the following query parameters:

• format: Specifies the output format. Supported values are text and json. The default is json.
• metrics: A filter to restrict the output to specific metrics.

Please note: The output format text has the content type text/plain; charset=utf-8.

Solved Bugs

• Fix for not refreshing the items of a collection after uploading files via drag & drop
• Fix the display of objects in the detail view even though there is no read permission

Patch releases

Version 4.49.1

• Fix the display of files in Detail View in Eticket
• Fix not working subpanels in module explorer "detail" views

Version 4.49.2

• Fix not showing app icons in App Management

Version 4.49.3

• The token based session registration (GET /api/session/tokens/register/{token} and GET /api/session/tokens/{token}) does not meet our security requirements and is now disabled, the endpoints answer with 404. A replacement is planned
  Integrations that still depend on them can re-enable the endpoints (more details)