Release Notes

The MBean HealthManager now also transmits information to the web applications that are included in the delivery of FirstSpirit as standard.
The file server-incidents.log (downloadable in FirstSpirit ServerMonitoring under “FirstSpirit / Monitoring / Codes” via the envelope icon) now also contains the following information:

• registrations of the standard web applications
• complete failure of one or more of the standard web applications

Example log messages:

WEBAPP INFO 15.09.2021 14:43:59.037 (de.espirit.firstspirit.server.ServerManagerImpl)
   Web application started: fs5root
RUN_LEVEL INFO 27.09.2021 09:09:44.091 (de.espirit.firstspirit.server.RunLevelHolder)
   Reached run level: CORE_WEBAPPS_STARTED(080)

Further, the MBean HealthManager now also considers the free hard drive space for the calculation of the server status.
For all writable and file systems involved on the FirstSpirit server, there are now separate MBeans that can be shown below HealthManager MBeans. The relative path in the server directory is used as the name.

If the free space in one of the file systems involved falls below 5% of the file system size or 640 MB (depending on which value is smaller), the server is deemed to be degraded, and a warning is issued for the respective file system.
If a warning e-mail is configured in the FirstSpirit ServerManager in case of insufficient available hard drive space (under Server properties / Global server properties / “Warning at”), the percentage is used as a warning limit for the MBeans instead.

Insufficient hard drive space is also recorded in the file server-incidents.log, e.g.

Insufficient free space on '/home/fsserver/Daten/CMSServer4/work
   (name=tmpfs, type=tmpfs)' detected, 185.801 MB left on file store.

Additionally, the MBean HealthManager now also checks the load on the server: if it is too high (e.g., as long as more than 5% of the processor time is used for garbage collections), the server is also deemed to be degraded. The exceeding and then dropping below the limit is recorded in the file server-incidents.log, e.g.

High Java VM garbage collection overhead detected: 5.30 %

The status of the MBean HealthManager of the server is now also visualized in the FirstSpirit Health Center (in FirstSpirit ServerMonitoring). There, it is possible to read directly in the status bar above the respective server name in the “FirstSpirit landscape” whether the server is in a problematic state.
The color and symbol coding is now as follows:

The checkmark on a green background means that the server is not reporting any current problems.

The exclamation mark on a yellow background means that the server is not reporting any current problems. However, the license will expire in the next 30 days and should be renewed.

The exclamation mark on a red background means that the server is in the degraded state.

To reduce dependency on Oracle's Java development and also so that longer-term plans can be made for the benefit of our customers, e-Spirit has increased its focus on the use of OpenJDK for some time, especially from manufacturer AdoptOpenJDK. All AdoptOpenJDK binaries and scripts are licensed in Open Source and available free of charge.

In approx. April 2021, the project “AdoptOpenJDK” switched to the “Eclipse Foundation” and is now called Eclipse Adoptium. The JDK has the name “Temurin”.
The latest releases can be downloaded from https://adoptium.net.

See also AdoptOpenJDK-Blog.

Further, Java 17 was published in mid September. JDK 17 is offered by most providers as Long-Term-Support (LTS) version. It follows Java 11, which currently has LTS status.
Internally, the first preparations were made for the test phase for the use of Java 17 (Temurin) with FirstSpirit. The objective is to release Java 17 in a future FirstSpirit release for use with FirstSpirit.

The “FirstSpirit Image Recognition” module now supports, in addition to the “JPEG” and “PNG” formats, images in “WebP” format:
During the upload, the images are now analyzed, the corresponding metadata is set (if configured) and the focus is set or automatically cropped.

When using the editorId function, forms in ContentCreator are opened in the current language by default (#global.language).
The new parameter

language

can be used to specify a language in which a form should be opened.

The parameter expects the abbreviation of the language or the language object, e.g.

<div$CMS_VALUE(editorId(editorName:"st_text", language:"FR"))$>
<div$CMS_VALUE(editorId(editorName:"st_text", language:#global.getLanguage("FR")))$>

For more information about the editorId function please see

• https://docs.e-spirit.com/odfs/template-develo/content-highlig/use-projects/index.html
• https://docs.e-spirit.com/odfs/template-develo/template-syntax/functions/instructions/editorid/index.html

Currently, the functionality of the “Data source management” in ContentCreator is still in Beta phase.

The following improvements have been made with the current release based on customer feedback:

• Columns containing the input component CMS_INPUT_DATE are now also displayed in the table view.
  When mapping to the data types Date or Long, sorting is also possible.
• In the data source management of ContentCreator, for media of type “File”, the name is now displayed in the table view (instead of a type icon as before).
  “Broken references” are visualized in red font.

For common information about the Beta phase of the “Data source management” in ContentCreator, please see the release notes for FirstSpirit 2021-08 (https://docs.e-spirit.com/odfs/releasenotes/2021-08/FirstSpirit_Releasenotes_EN.pdf).

FirstSpirit 2021-10 supports the following module versions for “FirstSpirit Content Experience Tools”.

* These modules require FirstSpirit 2020-03 or higher from this version.

Via the parameter

allowedRedirectHosts

URLs to which redirecting is allowed can be defined.
The status pages that can be set up for the CXT platform and the FragmentCreator (each under ~/status) now also check the configuration of this parameter.
The parameter can be configured in FirstSpirit, e.g. in the file fs-server.conf.

If the configuration is incorrect (which means the current host is not configured with the parameter allowedRedirectHosts), an error message is recorded in the log and a corresponding error message is displayed in the browser console.

Note on the status page in the event of an error:

External hostname is not allowed as a redirect host in the FirstSpirit server configuration.

With the new parameter cxt.platform.firstspirit.connection-timeout, a time limit (in seconds) can be defined for the FragmentCreator, after which the FirstSpirit connections are disconnected automatically again when they are no longer in use.
The parameter can be defined in the file web.xml of the WebApp component “FragmentCreator”, which is configured in the matching global web application for the FragmentCreator (“FirstSpirit ServerManager / Server properties / Web applications”):

or in the properties file cxt-fragment-creator.properties.

A value that is too low can result in that users are unexpectedly logged out. However, a high value maintains multiple connections when users close their browser without logging out.

The default setting provides that connections are automatically disconnected after 12 hours when they are no longer in use.

Excerpt from the default web.xml:

<context-param>
 <param-name>cxt.platform.firstspirit.connection-timeout</param-name>
 <param-value>43200</param-value>
</context-param>

The following modules and extensions are compatible with FirstSpirit 2021-10:

The interface WorkflowAgent (FirstSpirit Developer-API, Package de.espirit.firstspirit.workflow) was expanded with the method

isTransitionAllowed

This method determines if a transition can be executed by a specific user on a specific store element.

In contrast, the method getTransitionPermission (Transition transition) in the interface WorkflowPermission (FirstSpirit Access-API, Package de.espirit.firstspirit.access.store.templatestore) determines the authorization of a transition, but potentially modifies the permission model and generates a new WorkflowTransitionPermission, when no permissions have been defined for the respective transition yet. The API documentation has now been clarified with the current release at this point.
Instead, the new method isTransitionAllowed should now be used.

The method

isWorkflowAllowed

of the interface StoreElement (FirstSpirit Access-API, Package de.espirit.firstspirit.access.store) can be used prior to starting a workflow to test if starting is categorically permitted for the respective workflow and the respective store element.

With API, the page references of a page can now be determined with the convenience method

<page>.getPageRefs()

(FirstSpirit Access-API, Package de.espirit.firstspirit.access.store.pagestore, Interface Page)

As of the current release, the following internally used software has been updated:

• Spring Boot (used for MicroApp Framework)
  Update to version 2.5.4

The current release now includes a new method that makes it possible in a template from an Entity (which, for example, is generated by the “contentSelect” function) to receive a Dataset:

getDataset

This method expects the input of a reference name of the respective table template in quotation marks, e.g.

getDataset("products.product")

If the Dataset cannot be determined, null is returned.

Example:

$CMS_FOR(_entity, cs_press_releases)$
    $CMS_SET(_dataset, _entity.getDataset("products.product"))$
    $-- ... --$
$CMS_END_FOR$

Here cs_press_releases is the variable / identifier of the contentSelect function, products.product is the reference name of the table template.

Alternatively, the following notation can be used. In this case, the conversion already takes place when the FOR loop is called.

$CMS_FOR(_dataset, cs_press_releases.map(entity->entity.getDataset("products.product")))$
    $-- ... --$
$CMS_END_FOR$

For more information, see:

• https://docs.e-spirit.com/odfs/template-develo/template-syntax/data-types/entity/index.html
• https://docs.e-spirit.com/odfs/template-develo/template-syntax/functions/header/contentselect/index.html

As of the current release, the JSON output now also includes information about section validity periods, if available.
For this purpose the new attribute

lifespan

has been introduced.

If a certain validity period is set, the additional attribute lifespan is output with the section.

This attribute always has a value for the start time:

...
"lifespan": {
                  "start": "2021-10-15T14:00:00Z",
                }

For unlimited validity periods, no end time is output.
For validity periods with a time limit, the end time is also output:

...
"lifespan": {
                  "start": "2021-10-15T14:00:00Z",
                  "end": "2021-12-31T23:59:59Z",
                 }

Example output of a section:

{
               "fsType": "Section",
               "name": "cms_input_text",
               "displayName": "CMS_INPUT_TEXT",
               "identifier": "1df5eccf-c5ac-40ab-805a-6411c8dc3b69",
               "lifespan": {
                  "start": "2021-10-02T11:46:06Z",
                  "end": "2021-10-03T11:46:09Z"
}