Release Notes

With FirstSpirit 2021-09, the release interval was changed from monthly to every 4 weeks.
It is planned to adjust the name of the releases to this condition at the turn of the year to 2022: to create releases with more flexibility, the release name wil no longer base on the digits of the month (e.g. FirstSpirit 2021-12) but will use a continuous counter. The digits of the year are separated from this counter with a period, e.g.

2022.1

for the first release of the year 2022.

The release name is used in familiar places such as info dialog boxes.

When updating the uses of modules (FirstSpirit ServerManager / Server properties / Modules, “Update uses” / “Updating”), project components of deactivated projects are now no longer considered.

Furthermore, the administrator is notified during the reactivation of a project (FirstSpirit ServerManager / Project / Reactivate), if it uses a project component for which the module is not (no longer) installed on the server. In this case, he can remove the project component or install the module.

The status of elements is displayed in the menu bar at the top right. There – depending on the respective element type and status – different actions can be executed, e.g. starting and continuing workflows, displaying earlier versions of a page, etc.
Until now, the status for selected media and datasets was found in the “Dashboard”.
With the latest release, the design of the status display has been revised to also be able to take the status of media and datasets as well as multi-selections into account.

Which information and actions does the status display offer?
In addition to information for the respective element, the status shows information on the last change.
Available workflow actions are visualized via button.
Below the colored status information, it is possible to open additional views for pages (e.g. earlier versions of the page, hidden or deleted sections) or rectify validation problems.

Which element does the status apply to?

• In the preview (which means on a page), the displayed status refers to this page.
  Additional views of the page (e.g. an earlier version) can be opened with the corresponding buttons.
• In the Media management or the Data sources view, the displayed status refers to the respective folder that is selected in the navigation bar.
  For elements that are located in this folder and that were selected by clicking (media, datasets or other folders), the status and available actions are shown below as own status entries (visualized with arrow down).

In the Media management and Data sources view, multiple elements can be selected via click and workflows can be started on them. A bent corner indicates that a selection has been made and the status display applies to the selected folder and at least one selected element located in it.

If several of the selected elements are in the same workflow step, the workflow is activated for them at the same time by pressing the corresponding button.

Further information on operation
A click on the status icon or the “Show status report” button fixes the status display: this way, it remains open when changing to other elements so that the status of each desired element can be checked conveniently.
The display remains open until the user clicks on the status button again or opens another report.

The function of the “Status notifications” was visually adapted to the new design of the status display (“Status notifications”: plug-in, FirstSpirit Developer API, package de.espirit.firstspirit.webedit.plugin.status).

Status information is no longer displayed in the “Dashboard”. Until now, status information was displayed there for elements of the Media management and Data sources.

For more information, see also https://docs.e-spirit.com/contentcreator/menu-functions/element-status/index.html.

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

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

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

The following internal software has been updated in the latest FirstSpirit release:

• AWS SDK (Amazon API for automatic image recognition, used in the “FirstSpirit Image Recognition” module)
  Update to version 2.17.58
  With this update, more attributes can now be identified and saved for images with an analysis via the “FirstSpirit Image Recognition” module.
  Also refer to Amazon Recognition News.
• Apache Batik (Display, creation and manipulation of scalable vector graphics, SVG)
  Update to version 1.14
• TwelveMonkeys ImageIO (extended Java support for image file formats)
  Update to version 3.7.0

With the latest release, the JSON output now also contains information for pages on whether the “Page is completely translated to this language” checkmark is activated in the SiteArchitect or not.

SiteArchitect: "Page is completely translated to this language” option

If the checkmark is activated for the current language of the page, the value of the associated attribute is translated true, if the checkmark is not activated for this language, the value is false, e.g.

{
    "fsType": "Page",
    "name": "translated_status",
    "displayName": "translated_status",
    "identifier": "c3af851b-7429-4d28-9487-ca6e4c3311e8",
    "translated": false,
    "uid": "translated_status",
    "uidType": "PAGESTORE",
    "template": {
       "fsType": "PageTemplate",
       "name": "pt_empty_page",
       "displayName": "pt_empty_page",
       "identifier": "7c020f2f-719c-4334-8efc-f44015333d2a",
       "uid": "pt_empty_page",
       "uidType": "TEMPLATESTORE"
},
...

The display of objects (pages, sections, datasets, media, etc.) can be influenced at many places of the FirstSpirit Clients, such as in search result lists, reports, selection dialogs, etc. The so-called “Snippets” are used for this. The configuration occurs on the “Snippet” tab of the respective template, for media on the “Snippet” tab of the selected metadata template for the project.

With the latest FirstSpirit release, the syntax of snippet definitions is now checked during saving. If it is incorrect, a corresponding note is displayed and the template cannot be saved.
Example for an error message:

Incorrect syntax in Extract definition
... (at line 4, column 48)

Note: Only the general syntax will be checked. However, there is no check to verify that the variable names that are used are correct and if the applied methods and operators are compatible with the respective object type.