DAM Release 4.27

March 2025

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

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

• Accessibility: To further improve compatibility with screen readers, we now better label (non-) clickable icons, navigation, header and footer, and support alt text for images.

Technical Changes

New Field Folder in the Files Module and Automatic Creation of a File-Folder Relation

To make it technically easier to maintain the link between a file and its folder, we have added a new database field folder to the Files module. This field contains the identifier of the folder in which a file is stored. It is automatically updated each time a file is uploaded or moved.
Please note: This feature was previously provided by 4App File-Folder-Relation.
What to do: Remove 4App File-Folder-Relation, if installed, to improve performance.
Upgrade script: When you upgrade, the folder field is automatically created, and all existing files are automatically linked via an upgrade script.
What to do: For the script to work, you must check your custom folder in module Files for a custom field folder and rename or remove it in the database and configuration files before upgrading. Check your database for custom table file_folder_fc and remove it.

File Preview Processors Error Handling

We have improved the error handling for file preview processors. If a file processor cannot be processed, an error is now logged in the Request Management rather than in the Application logs.

Removed Deprecated Endpoint

We have removed the deprecated download endpoint URL /service/v2/filetransfer/filetransfer/download?id={id}&session={session}.

New Open API Endpoint / Deprecation of Class FolderPreTaggingService

We have added a new Open API endpoint /api/extensions/dam/pre_tagging/{id} to perform the folder pre-tagging operations:

• GET to get the folder pre-tagging for the given id. If an optional query parameter merge is true, the result will also include the inherited pre-tagging.
• PATCH to update the folder pre-tagging for the given id. The result of the PATCH operation is the number of updated files, depending on the optional query parameter apply:
  • NONE to update only the folder pre-tagging (default behaviour)
  • ONLY_SAME_FOLDER to apply the pre-tagging to files in the updated folder
  • WITH_SUBFOLDERS to apply the pre-tagging to files in the updated folder and all its subfolders

This new endpoint replaces the following methods, which are now deprecated and will be removed in the future:

• set_pretagging (which was added to AMF method handleRequestSingle)
• get_pretagging (which was added to AMF method handleRequestSingle)

Solved Bugs

• Fix for the version upload import tagging: Users can now always decide whether to perform the import tagging (if configured for their role), not just for folders that allow uploads.
• Fix inconsistent display of the "Compare images" toolbox action in the Version module when selecting two archived versions as opposed to selecting one archived version and the current version
• Fix transaction for handling files and folders, e.g. when moving folders via the frontend. Changes to the database are now only visible when the transaction is complete.

Patch releases

Version 4.27.1

• Fix reduce transaction size to avoid error java.sql.SQLException: Error on observer while running replication hook 'before_commit' in update script 123LO

Version 4.27.2

• Fix deadlock with synchronized file operations