Release Notes

With the latest release, you can now check if the available disk space is sufficient when importing a project (FirstSpirit ServerManager | Project | Import).

If the “Check for sufficient free disk space” checkbox is activated, a check will run before the import to determine if there is sufficient disk space for the project import without reducing the free memory enough to cause the FirstSpirit Server to shut down.

Note: In case of this check, it is assumed that there are no database contents that occupy the available memory of the FirstSpirit. Furthermore, this check estimates the additionally required disk space beyond the pure data storage (e.g., for the search index, relation graph, etc.). In rare cases, it is thereby possible that the server shuts down in spite of this check due to a lack of memory.

See also https://docs.e-spirit.com/odfs/edocs/admi/firstspirit-ser/menu-bar-items/project/index.html#text_bild_3.

Generation type detection by the AWS S3 Deployment module has been improved (full or partial generation), e.g.,

INFO  18.03.2022 17:31:11.365 {uID=0,seID=885317,pID=881777} (com.espirit.ps.aws.
   services.s3.GenerationType): Generation type was set to [full | partial generation]. 

In this context, new methods have been created in the FirstSpirit Developer API in the de.espirit.firstspirit.scheduling package, ScheduleTaskExecutionContext interface, that allow access in a ScheduleTaskApplication to the executing ScheduleTask:

getTask();
getTaskIndex();

In addition, the automatic recognition of the generation type has been improved:

• Until now, a decision was made based on the first generation action (or the first generation task) whether or not files must be deleted from the S3 bucket. The action / task was thereby taken into account regardless of whether it was active or not.
• Now, all active generation actions that occur in the sequence prior to the S3 Deployment Task are taken into account. If one of these actions is a partial generation (“partial generation”), a deployment is executed without deletion.

The deployment can now be configured using a newly implemented drop-down box based on the individual project requirements (“Deployment options”), within the project component and / or within a AWS S3 Deployment action (in “Schedule management”)

• (Empty)
  The setting from the project component is used (AWS Services Configuration ProjectApp).
• Auto detect (any partial generation leads to Deploy only):
  The automatic recognition is used (see explanation above):
  The review includes all active generation schedules that occur in the sequence prior to the S3 Deployment Task. If one of these schedules is a partial generation (“partial generation”), a deployment without deletion is executed.
• Complete sync (with deletion, use with full generation only!):
  The S3 Deployment is executed with deletion of obsolete files in the S3 bucket.
  This option should only be selected for full generations.
• Deploy only (no files will be deleted, usually used with partial generation):
  The S3 Deployment is executed without deletion of obsolete files in the S3 bucket.
  This option is generally used for partial generations.

Note: It is recommended to select the suitable deployment type for the individual project requirements from this drop-down box by hand and not to use the automatic recognition.

More information

• on module: https://docs.e-spirit.com/cloud/developer-cloud-documentation/Cloud_Development_Deployment_DE.html
• on generations: https://docs.e-spirit.com/odfs/advanced-topics/generation/index.html

The display of available web applications and web components has been improved (FirstSpirit Server Manager/“Server Properties/Web Applications” and “Project Properties/Web Components”):

If it is not possible to display all web applications/components at the same time due to the width of the dialog, you can now use the arrow symbols to scroll through the elements:

You can use the following icon to display the elements as a list:

In the past, all existing web applications/components were displayed in multiple lines underneath each other when the width of the dialog was too narrow to display all elements at the same time.

The new display method also builds the display (especially in case of many web applications/components) significantly faster than before.

The new generate.defaultMaxStackSize parameter can be used to define the default value for the stack size server-wide in the fs-server.conf file.

Default value: 75.

In the past, the default value specified by the #global.maxStackSize parameter was 50.

For more information, see

• generate.defaultMaxStackSize parameter: https://docs.e-spirit.com/odfs/edocs/admi/firstspirit-ser/configuration-f/firstspirit-ser/area-server/index.html#generate_defaultmaxstacksize
• Stack depth in FirstSpirit: https://docs.e-spirit.com/odfs/template-develo/template-syntax/system-objects/global/preview-specifi/index.html#_global_maxstacksize

With FirstSpirit 2022.3, the support for the “Legacy mode” for FirstSpirit Server and module developer has been discontinued.
With the latest release, the support for the “Legacy mode” was also removed in the FirstSpirit Module Gradle Plugin (firstspirit-module-gradle-plugin-[version].jar). The current version of the plug-in is 4.0.0.
With this version, only module-isolated.xml files are now generated. However, modules that contain a module.xml file cause an error message when generating.

The performance when calling the Amazon Recognition API has been improved:
Recognition of faces and celebrities is now only executed when labels such as Human, Person or Face have been recognized first.
Likewise, text recognition is only executed when a Text label has been recognized first.

Based on Debug log output, you can now track which API calls are made, e.g.,

... Calling the 'detectLabels' Amazon Image Rekognition API endpoint
... Calling the 'detectFaces' Amazon Image Rekognition API endpoint

As part of this change, the AWS SDK has been updated to Version 2.17.173.

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

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