Release Notes

As of the release 2026.8, the following internally used software has been updated.

• Spring Boot
  Update from version 4.0.6 to version 4.1.0
  • CXT Platform
  • ContentCreator
  • Template Development MicroApp
  • Collaboration
  • Analyze Assistant
  • Multisite Management
    

The encryption and compression of the FirstSpirit connection can now be controlled via the global CLI options --conn-encryption and --conn-compression, as well as through the environment variables fsencryption and fscompression. If no value is specified, the FirstSpirit default values will continue to apply.

The FirstSpirit server now supports OAuth 2.0 Protected Resource Metadata according to RFC 9728.

If the file oauth-protected-resource.json is stored in the configuration directory conf, the server provides its content unchanged and without authentication at <FSURL>/.well-known/oauth-protected-resource, allowing clients to address FirstSpirit as an OAuth resource server.

Changes to the file – including creation and deletion – take effect immediately without a server restart.

Modules can be deactivated and reactivated in the ServerManager as well as via the FirstSpirit Access API.

A deactivated module is removed from the server's runtime environment – its services are stopped, and its web and project components are no longer considered – while the configuration is fully preserved. This allows problematic modules to be taken out of operation without uninstalling them. The deactivated state remains even after a server restart.

FirstSpirit 2026.8 supports the following module versions for FirstSpirit Content Experience Tools.

The FirstSpirit REST API is still in the open beta phase and is now also available in version 0.0.16-beta via the Download Portal. From now on, it will be updated here with every FirstSpirit release.

Please refer to the instructions in the Rezolve Support Portal. There you will find, in addition to the preliminary installation guide and the release notes, the download link for the current version. This requires access to the Artifactory.

The new method getPreviewPageRef in WebeditUiAgent now allows querying the contextual PageRef for the current preview page, if available. This differs from getPreviewElement, as in the case of a content projection, a dataset may also be returned there.

Messages in collaboration conversations can now be deleted.

Deleted messages are replaced by the placeholder "This message has been deleted." so that the conversation history is preserved; the original content is no longer delivered. Deletion is only possible for the creator as well as project and server administrators, similar to editing; system and AI messages are excluded.

As soon as all user messages in a conversation are deleted, the conversation is automatically set to the status "resolved" and can no longer be edited. Deleted messages can be restored via the API if needed; however, the "resolved" status of a conversation is not automatically reversed as a result.

With BundleAgent#deployBundle(bundle), a bundle rollout can be started and the progress can be tracked via the returned DeploymentProcess object.

A running deployment can be retrieved at any time via BundleAgent#getDeployment(bundle). If no rollout is active, a NoActiveDeploymentException is thrown.

More information can be found in the Multisite Management Documentation.

In the input components CMS_INPUT_RADIOBUTTON and CMS_INPUT_CHECKBOX, options available within ENTRIES can be defined. If a description is maintained for these options, it is now displayed as a tooltip on the respective options.

Example:

<CMS_INPUT_RADIOBUTTON name="radiobutton">
   <ENTRIES>
     <ENTRY value="option">
       <LANGINFOS>
         <LANGINFO lang="*" label="Option" description="Tooltip" />
       </LANGINFOS>
     </ENTRY>
   </ENTRIES>
   ...
 </CMS_INPUT_RADIOBUTTON>

When creating, moving, and deleting paragraphs in the ContentCreator, language-dependent permissions are now taken into account. For these structural changes to the page, the permission "language-independent" is required - analogous to the behavior of language-independent FS_CATALOG input components in the form view.

In template development within ContentCreator, the properties of styles can now also be edited (e.g., font, font size, font, border and background color, as well as tooltip).

Further information can be found in the documentation.