Release Notes

By default, when a user authenticates via an external provider (e.g. LDAP, SAML Identity Provider), the complete group information that is transmitted is stored in FirstSpirit.

Via the new

externalGroupFilter

parameter which is defined in fs-server.conf, it is now possible to define via a regular expression which subset of this group information should be taken over by FirstSpirit.

Example:

externalGroupFilter=.*(csm_admin|FirstSpirit).*

With the current release, FirstSpirit provides templates for all languages supported by the Java version used by the FirstSpirit server.

Language templates

When defining external groups, since FirstSpirit version 2022.12 it is possible to use a placeholder in the form

${name of the placeholder} 

can be defined. This placeholder is replaced accordingly during the project import.

The placeholders can be defined as -D parameters in fs-wrapper.isolated.conf, as variables of the operating system, in fs-server-aux.conf or fs-server.conf (with decreasing priority). Variables that are passed to the FirstSpirit Java process as -D parameters thus have the highest priority, while variables defined in the fs-server.conf are overwritten by all other places (see FirstSpirit ServerMonitoring / FirstSpirit / Configuration / Server (→Documentation for Administrators)).

Example (with 3 wildcards):

cn=${developer},ou=${department},dc=${company},dc=com

Note: This function is useful in connection with project templates (see FirstSpirit ServerManager / Menu bar items / Project (→Documentation for Administrators)).

For FirstSpirit servers on which projects are frequently created that are based on the same foundation (e.g. predefined groups, users, orders, templates, ...) there is now the option of creating corresponding project templates that can be selected when a new project is created.

This menu item is only available to server administrators.

A project template can be created by setting up and exporting a project accordingly.
Note: The name of the project is used as the display name of the template.

The project export file must be stored in the <FirstSpiritROOT>/data/templates/projects directory.

When creating a new project the Project template field is only displayed if project templates are also stored on the FirstSpirit server. The project templates stored there are offered for selection in a drop-down input component.

Project – Create from template

If one of these projects is selected, the corresponding project will be imported (orders will be activated, any existing schemas must be linked to the corresponding database layer).

For more information, see FirstSpirit Manual for Administrators, chapter “Project”.

The Tailored UI is now server-wide configurable using the “Feature Configuration Service”, project-specific settings are no longer mandatory.

For projects to which the project component “CXT ContentCreator Extension: Feature Configuration” (“FirstSpirit ServerManager / Project properties / Project components”) is or was added, the configuration made there is taken into account. For projects without this project component, the configuration of the Feature Configuration Service is taken into account.

Existing configuration made at project level before an upgrade to FirstSpirit 2022.12 is still valid after an upgrade to FirstSpirit 2022.12. If a configuration is to be made at server level, the project component “CXT ContentCreator Extension: Feature Configuration” must be removed for the project or projects concerned so that a configuration made at server level takes effect in the project. To adopt an existing project configuration at server level, the From Project button can be used.

FirstSpirit 2022.12 supports the following module versions for “FirstSpirit Content Experience Tools”.

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

The MicroApps API was changed: new methods were added and one method was renamed. This concerns the JavaScript objects

CxtMicroAppBridge
CxtMicroApps

Querying possible MicroApps was previously done using the method

getButtons

This method has been renamed to

requestMicroAppActions

With this query now a list of

contextTypes (optional) 

and

clientIds (mandatory field) 

can be passed.

MicroApps define themselves which contextTypes and clientIds they support.
Possible clientIds are for example

content-creator or 
fragment-creator

Example
previously

window.CxtMicroApps.getButtons(context).then(...)

now

window.CxtMicroApps.requestMicroAppActions(clientId, contextTypes, context).then(...)

With the current FirstSpirit version the unique GID of a project is displayed in the project properties. This GID can be copied but not changed.

The unique GID of a project

With the current FirstSpirit version, the following, internally used software has been updated:

• JxBrowser (Chrome browser engine for displaying the integrated preview in FirstSpirit SiteArchitect)
  Update to version 7.27
  The engine now uses “Chromium” in the version 102.0.5005.167.