8.0.1

We recommend you use at least version 8.0.2, which contains several bug fixes.

Download formcycle | Frontend server | Frontend server (inbox) | Checksums

Small improvements

• New filter options in the form overview for frontend servers. With these new options you can limit the displayed forms to only those forms that are available on a certain frontend server.
• When a form record was deleted, the protocol now includes the reason why the form record was deleted.
• When searching for form record attachments in a workflow action, you can now also use placeholders.
• New plugin type that allows plugin developers to offer additional form element templates in the form designer.
• New plugin type that allows plugin developers to offer additional preconfigured workflow actions and events in the workflow designer.

Changes

• No protocol entries are created anymore for failed control flow actions (such as conditions or switches), when the failure was caused by a child element (such as an email action). This sometimes resulted in confusion as it was unclear what a failed control flow action means. For the failed action itself, a protocol entry is still created.
• Links in invitation email for a client now use the configured base URL of the client. When an administrator invites a user and accesses formcycle via an internal URL, the invited user might not be able to open the link otherwise.
• HTML data attributes are now allowed in the form designer and in the preview.
• The appointment finder does not show the selected  date anymore when no time is selected.
• Verification emails that are sent to users to confirm their email address now contain a link that takes the user to a confirmation page with a confirmation button. Previously, the email address got confirmed as soon as the user clicked on the link. This is problematic as some email clients open links automatically, e.g. in order to check their content for security reasons.
• Improved error messages in web forms, when the automatic upload feature is enabled and the upload fails due to a network error.

Bug fixes

Web forms

• When the form contains an input field with a datepicker, it is now possible again to switch between form fields with the tab key in the when using the Safari browser (or other WebKit based browsers).
• The selected appointment in the appointment finder can now be cleared as well on a mobile device with a low resolution.
• When a favicon (web page logo) is defined in the meta area of the form designer, the default formcycle favicon is now omitted. The custom favicon was not displayed is some browsers otherwise.
• The selected background color for a fieldset is now applied to entire area of the fieldset.

Form designer

• Invisible containers do not receive the CSS class XContainer automatically.
• Fixed an issue where forms could not be opened in the form designer in rare cases.
• All values are displayed correctly again when submitting a form in preview mode.
• Pages can be inserted into the form even when all existing pages have been deleted.
• When saving a form, the designer now validates for duplicate names and aliases in form variables as well.
• When conditions such as Required-If are used  that reference form variables, it could sometimes happen that the configured conditions were lost when the form was opened in the form designer again and saved afterwards.

Workflow designer

• Form variables are show again in the  placeholder dialog within the workflow designer.
• When the workflow is saved, the last modification date and the user who last modified the form are updated as well.

Inbox

• When the refresh button is pressed, the list of available forms now also gets reloaded.

Login services

• Fixed an error that sometimes prevented users from signing in.
• For login services of type SAML 2.0, it is now possible to download the service provider metadata even when no identity provider metadata were uploaded yet. Note that when you create a new login service in the backend, you may have to save the login service first. 
• Changes to the client administrator role (that can now be made in the client menu as well) are saved correctly.
• The custom UI of login services provided by a plugin is now shown correctly even after the first login to the formcycle application.
• When importing a form with configured login services, the services are now correctly resolved against the existing login services.
• A never-ending loading dialog that could sometimes occur in the login services menu cannot show up anymore.

Backend

• An issues with the user migration during the update from version 7 to version 8 was fixed.
• The database update now works correctly again with the Oracle database management system.
• Long plugin descriptions can now be expanded and collapsed. Initially they are collapsed.
• The form store is displayed correctly after the formcycle application was restarted.
• When the license is updated, the corresponding formcycle version now gets updated as well again.
• The frontend server entry is shown in the menu only if the license allows it.
• Entering spaces in the ID filter for protocol entries does not result in an error anymore.
• An issue was fixed when making a copy of a form that uses the old workflow for the new workflow. The copy could not be created when the existing form contained an additional state with the name Received.
• The loading time for the plugin menu was improved.
• The Word-Fill action now creates checkboxes correctly again when a table cell contains more than one checkbox placeholder. 
• The formcycle logo is not shown twice anymore for cloud installations.

For plugin developers

• Implementations of IPluginWorkflowNodeHandler should now implement INodeHandler#isCreateProtocolEntryAfterExecution(ICreateProtocolEntryAfterExecutionParams params) instead of the deprecated method INodeHandler#isCreateProtocolEntryAfterExecution(boolean). Note that usually neither method is implemented for business logic actions, as there exists an appropriate default implementation.
• Login service plugins that required a custom PAC4J state generator(org.pac4j.core.util.generator.ValueGenerator) can defined such a generator by returning a custom implementation of org.pac4j.core.client.Client that also implements the interface de.xima.fc.interfaces.auth.pac4j.IStateGeneratorProviding.
• The new plugin interface IPluginFormElementTemplate, can be used to offer additional form element templates in the form designer. 
  • The plugin also receives the current project as a parameter, which allows plugins to offer templates only for certain forms.
  • Plugins that only wish to provide static templates stores as class path resources in src/main/resources, the mixin IPluginFormElementTemplateStatic can be used to simplify the implementation.
• The new plugin interface IPluginWorkflowElementPrototypes can be used to offer preconfigured workflow elements in the drawer panel to the left of the workflow designer. Previously this was only possible for plugins that added a new workflow element type (trigger or node).