Core Engine Release 4.25

December 2024

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

New Field Renderer Type "StaticText"

We have added a new field renderer type to display static text without the need for an attached metadata field. The new "staticText" type can be used to place e.g. description texts anywhere in an object renderer. If set in the field renderer attributes, HTML is also supported (default: false).
Further information: StaticTextRenderer documentation

New Visual Type for OnOff Renderer

We have added the option to select a visual type for the OnOff renderer. New visual type "checkbox" allows a value to be set via a checkbox. The boolean switch remains the default if no visual type is set.
Please note: The field is nullable by default, displayed with an "X" to remove a set value.
Further information: Object Renderer documentation

Change Event Table Pruning

We now check all change event tables ({module}_chg_evt) on a daily basis and clean them of completed entries older than 30 days.
Further information: Event Management documentation

Error Handling Improvements

We have further improved the error handling and replaced some custom error messages with the new OpenAPI ErrorResponse.

Solved Bugs

• Fix ignoring fonts from the global/fonts folder when generating a preview for PowerPoint documents
• Fix not loading all fonts into the Java GraphicsEnvironment due to a missing support for uppercase file extensions. These are now supported
• Fix not working option to interrupt search hooks/manipulate responses. Developers can now interrupt the execution of before and after search hooks by either setting the response status to COMPLETE (for BEFORE_SEARCH and AFTER_SEARCH) or throwing a ReturnCurrentResult exception (for BeforeSearchEvent and AfterSearchEvent). The response continues with modified properties.
• Fix executing drop actions in PID trees more than once
• Fix poor performance when dragging over a PID tree
• Fix not resetting search parameters after refreshing the view (by clicking on the module tab or main logo)
• Fix downloading a file with an incorrect extension when using the "switchToJpegIfNotTransparent" conversion option for files without transparency