8.2.3

Release date

• August 19th, 2024

Download links

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

Minor features

• New monitoring bean (MBean) named FCVersion that lets you access the version number, the version name and the build date of the formcycle application.

Fixes

Backend

• Adjustments to the update from version 7 to version 8. Affects only systems that were not update to version 8 yet.
  • Fixed an error that occurred during the migration of users. When a client had LDAP users, but did not have an LDAP configuration, the users were created without a method to sign in.
  • The login services of forms and workflow state now get updated with LDAP login services if required. In version 7 of formcycle, the login service system login included both system users as well as LDAP users. In version 8, it only refers to system users. 
• Improved error message when a plugin update or installation fails due to a server error.
• When changing the database in the system database menu, the encryption details always get saved.
• The email server gets recognized correctly even when using an old email server configuration file.
• Fixed an issue with portal plugins where a portal page did not work correctly when opened immediately after a server restart with the automatic update setting enabled.
• When deleting a client and the checkbox to delete all client users is disabled, the users do not get deleted.

Inbox

• Migrating a form record to the current version is now possible even when the the setting to disallow submission in the inbox was disabled via the access dialog.
• Improvements when migrating a form record the current version in the inbox. The option was still available when the form tab was not selected, even though no migration was possible in that case.

Form designer

• Fixed an error in the form designer when the options of a select field were set to a data source and that data source did had a row with both an empty display name and an empty value.
• Fixed an issue where templates of type page could not be inserted in the form, when a form element or container was selected.

Web forms

• The appointment picker does not get cleared anymore when a container unrelated to the appointment picker had a hidden-if or read-only-if condition with the clear-if-hidden or clear-if-read-only option enabled.
• The keep-alive mechanism to keep the session alive now works correctly when the form is embedded into external pages via the AJAX embedding mechanism.

For plugin developers

• The menu entries of a IPluginMenuEntries are now limited to the scope where the plugin was installed. E.g. if the plugin was installed in the scope of a particular client, the menu entries are available only to that client.
• Minor adjustments to the lifecycle of portal plugins (IPluginPortal)
  • The portal context now gets initialized earlier, when the plugin is activated. Previously, that happened only when the first request to a plugin portal was made. This by itself should not have any observable effect on portal plugins. 
  • The destroy method of Filter and Servlet now get invoked when the portal context is shut down, i.e. when the plugin gets disabled.
  • Filter and Servlet that throw an exception in their init methods are not put into service anymore, as mandated by the servlet specification.
• Support ServletContextListener for portal plugins (IPluginPortal). If the JAR file contains classes that implement ServletContextListener, their respective contextInitialized and contextDestroyed method will be invoked when the portal context is initialized.