Core Engine Release 4.34

May 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

New Workflow Action for Merging Fields

In the context of workflows, we have implemented a new action for merging the contents of multiple fields. The configuration allows for custom handling of value options, languages, dimensions, and templates.
Please note: This feature was previously provided by 4App Search Extensions.
What to do: Remove 4App Search Extensions, if installed, to avoid compatibility issues.
Further information: Event Management "Merge Fields" Action

Improved Health Check in a Kubernetes Environment

If the environment is a Kubernetes and the running system is in maintenance mode, the health check endpoint /health will now respond with status 500 (Internal Server Error), meaning that the system is unhealthy.

Improved Derivateservice Error Messages

We have improved the error messages in the database for download failures caused by XMP or IPTC data to provide more detailed information in the Filetransfer database log.

Solved Bugs

• Fix incorrect filtering of special characters in fulltext search with MATCH_ALL comparator
• Fix unnecessary error message for new users on login because SaveJson returned "NaN" when parsing an empty string

Patch releases

Version 4.34.1

Technical Changes

Improved Execution of Update Scripts

To ensure a correct execution order of update scripts and to avoid errors due to scripts that are still in progress after a restart, we added new update script "099LO". It runs first after a restart and sets all update scripts with status "in progress" back to "intial". After that, the following scripts will execute completely one after the other.
If a script in progress is interrupted (e.g. due to a database error), administrators can manually set the status back to "initial" in admin snap-in "Update Management".

Solved Bugs

• Fix for executing update scripts although a previous update script returned status final success do restart. Now following scripts are only executed after a system restart.
• Fix for executing update scripts although a previous update script returned status in progress. Now the 4ALLPORTAL starts in maintenance mode and following scripts will wait (also compare this technical change).

Version 4.34.2

• Fix input of additional values in SelectionRenderer