Universal Messenger 7.51.0 (EN)

Owned by Florian Wolff
Last updated: Apr. 25, 2023
4 min read

Release 7.51.0 Build 1860 was released in January 2023. This release includes:

  • Monitoring REST Proxy and App usage

  • REST Proxy 3.1.0

  • Functional improvements and bug fixes

  • Update of various components

  • Optimization of the internal data model (update of the database schema, DB backup strongly recommended!)

  • Support for Java 8 and 9 will be discontinued as of Release UM 7.53

Preparations before starting the update

Several database schema adjustments are made when updating to UM Release 7.51.

It is therefore strongly recommended to create a complete database backup before running the installer. Furthermore, the update process should - as far as possible - be tested beforehand in a test or staging system with a comparable configuration.

Monitoring REST Proxy and App usage

Monitoring REST Proxy

With the update to version 3.1.0, the REST Proxy now periodically reports its state to the respective UM. With this, an overview of all active REST Proxies can be viewed in the backoffice under Tools / REST Proxy:

Monitoring App usage

The use of app forms – e.g. newsletter registration forms, contact forms, etc. – can now be logged by the UM so that the backoffice can track which App instances were accessed or submitted when and on which page.

This feature can be activated by setting the following configuration option in cmsbs-conf/cmsbs.properties:

cmsbs.plugininstance.usage.entries = 10

If usage monitoring is activated, the time of the last call is displayed in the App instance list:

In the respective edit view, the lastest calls are listed in detail:

Functional improvements

Copying Newsletter drafts

Newsletter drafts (see Newsletter / Send Newsletter) can now be copyied before being sent.

Total duration of newsletter sending

The total duration of a newsletter sending is now precisely determined and displayed in the Newsletter Archive. Interruptions are also taken into account (i.e. not counted), so that the send rate is reliably determined.

History Log

In the History Log, the name of the job is now displayed in the user column in the table view if the respective action was not triggered by a backoffice user but by a job.

Archiving of incoming emails

The archiving of incoming emails that can be assigned to a specific Entry is now automatically activated in new installations. It can be used with all licenses in the future.

In existing installations, archiving can be enabled by adding the following line to cmsbs-conf/additional.attributes:

include: cmsbs-conf/cse/api/plugins/de.pinuts.cmsbs.bouncemanagement/incoming_mail.attributes

In installations where this file is taken from the installer with every update (e.g. in Docker environments), this update may cause the incoming_mail.attributes file to be included multiple times. This leads to an error at startup, which can be fixed by removing the duplicate configuration line.

Core Scripting Engine

Automatically deleting files from virtual file system

Files in the virtual file system can now have an expiration date. When this date is reached, the files are automatically deleted by a background job.

const f = UM.fileSystem.getByPath('cmsbs-work/acme.com/some-file.json'); // Delete after two days: f.deleteAfter = Timestamp.addDays(Timestamp.now(), 2); f.save();

Bug fixes

Fixed a SQL error that could occur in the Dashboard view when using a Postgres database.

Sending to syntactically invalid email addresses via Amazon Simple Mail Service no longer results in the sending process being aborted.

Some database queries executed on the Newsletter detail page have been optimized.

Subsequent sending of a Newsletter to individual recipients after the actual sending process has been completed now works even if sending has been stopped in the meantime.

The preview function of various Apps (including Newsletter and Contact Form) now no longer uses the REST endpoint under /cmsbs/rest/, but rather the new endpoint /cmsbs/admin/rest/, which is only accessible to logged-in backoffice users. This means that the entire /cmsbs/rest/ path can now be blocked for access from the Internet for UM installations that can be reached from the public network.

After Tomcat 10.0, Tomat 10.1 is now also supported.

Update of various components

Support for Java 8 and 9 will be discontinued as of Release UM 7.53

As of Release 7.53, Java 11 or 17 will be required to run Universal Messenger.

Java 8 or 9 will then no longer be supported.

Note: Officially, only Java versions designated as Long Term Support (LTS) are supported.