8.5.6

Release date

• October 8th , 2026

Download links

• ⇩ formcycle (master server)
• ⇩ Frontend server
• ⇩ Checksums

Version 8.5.1 includes security-related improvements and updates.
We recommend all customers to update to this or a later version as soon as possible.

Also see the release notes of version 8.5.0, 8.5.1, 8.5.2, 8.5.3, 8.5.4 and 8.5.5

Changes

• Files with an upper case extension can now be selected in the workflow, e.g. file.DOCX for the action that fills Word files.
• The search for tags in the form overview menu is now case-insensitive.
• CSP headers configured for the backend under System → General are now also applied to the user portal UI.
• The chat completions prompt service now sends the system prompt, if one is set, as the first message, before the user's message.

Fixes

• Workflow action "Create text file" with output type CSV
  Texts from form placeholders containing line breaks are now enclosed in quotes.
• Workflow conditions and switches
  The alignment of condition names has been corrected.
• JavaScript documentation
  The documentation now clarifies that the error function added via $.fn.errorFunc returns an error message that is interpreted as an HTML snippet. This was always the case, but the documentation was not clear about it. If you include dynamic data in the error message, you must encode it properly for HTML.
• Login layout selection
  Different warning messages are now shown for login services that are not licensed and for login services that are not yet configured.
• Remote URL
  A byte-order mark (BOM) in CSV files fetched from a remote URL is now recognized and removed.
• Printing web forms
  If the browser supports it, a native CSS solution is used to resize a textarea to its content. This enables auto-resizing when printing a web form (on paper or as PDF) with additional margins or different zoom levels.
• Subject of form records
  Function placeholders in the configured subject of a form record are now resolved when the subject, the inbox or the data table is updated.
• Inbox
  Planned events from different form records were shown in the inbox by mistake. This has been fixed.
• Word/PDF export
  Initialization errors when exporting an inactive form version have been fixed.
• Login services (Oracle databases)
  Saving and updating empty attribute values now works.
• Read flag of form records
  Changing a form record's read flag is no longer treated as a modification. This resolves an error where a running workflow failed when the form record was marked as read or unread.
• Opening a form via /form/copy URLs
  An error occurred on submit when a form field was named fcpuid. This has been fixed.
• Localization
  A typo in the German localization of the message with the key appointmentNoSlotAvailable has been corrected.
• User portal uploads
  An error when uploading files whose file extension has a leading dot has been resolved.
• Backend requests
  Backend requests no longer slow down with the number of profile properties of the logged-in user.

For plugin developers

• The NPM packages @de-xima/fc-form-renderer, @de-xima/fc-form-designer and @de-xima/fc-workflow-flowchart are now published as ESM ("type": "module").
  • In most cases this will not affect your build. Depending on your build setup, you might have to adjust it slightly. This only matters if you build your plugin against a newer formcycle version. Plugins built against an older version will still work.
  • You might experience build issues if you use Jest as a testing framework, as Jest still does not support ESM directly. Add a transformer, or use an alternative testing framework such as vitest or the Node.js native test runner.
• The published NPM packages have been fixed. They already declared "type": "module", but some still used CJS syntax and some had missing file extensions. As a result, some build setups no longer recognized the provided exports.
• IPluginMessageService has two new default methods: supportsReplies(PluginMessageServiceSupportParams) and supportsUploadRequests(PluginMessageServiceSupportParams). Implement them to let the options "Allow reply" and "Request file" be configured for your message service. getFormRecordMessage() is deprecated in favor of new methods.
• IPluginSendMessageRequest has new methods for accessing the chat UUID, the message UUID and the upload requests of the message to be sent.
• Additional validation-related flags have been added to the parameters of IXItemBasic#validate and IXItemBasic#validateGlobal. This allows plugin widgets to exercise more fine-grained control over whether and when validation should be performed. Note that normally, you should still only check IXBaseValidationParams#isShouldValidate and skip validation when it is false. The additional methods are for advanced use cases, when validation must be performed even when it normally would not be.