X4 Server: Bug fixes 7.5.0

X4BUG-1303

If a process referenced in a timer-based intermediate event (Timer-based Intermediate) was renamed in a BPM process, the process name stored in the event was not automatically adapted. As a result, the event continued to use the old name. This bug is now fixed and when renaming a process, the reference in the event is correctly refactored and updated.

X4BUG-1568

When removing Processing Instructions from XSLT output, existing CDATA blocks could also be lost in version 7.4.x. This resulted in content no longer being output as CDATA as expected, even if it was explicitly configured in xsl:output. This bug is now fixed and CDATA blocks are retained and displayed correctly in the output when processing instructions are removed.

X4BUG-1641

With XSD using xs:import or xs:include elements referencing a remote resource, an error occurred. The elements could not be resolved if they were moved to a new URL and the call to the original URL responded with "Moved permanently". This bug is now fixed.

X4BUG-1653

During the schedule.xml migration, periods such as 180 m or 24 h were not correctly converted to cron expressions, resulting in invalid cron syntax and the associated processes not being started. This bug is now fixed and time intervals are correctly converted to valid cron expressions during migration.

X4BUG-1744

Swagger UI: We have cleaned up Swagger UI Services. In the course of the conversion to OIDC , the LoginService and the UserService were removed. In addition, the Keycloak Management Service has been discontinued.

X4BUG-1745

Swagger UI: The description for using API endpoints has been revised.

X4BUG-2099

Executions that are not started due to an instance limit reached (Instance limit = 1) are no longer displayed as errors in the Process Monitor. A meaningful message is displayed instead.