Data privacy notice

 

When this content is loaded, usage information is transmitted to Vimeo and may be processed there.

 

             

8.0.4

Modified on Wed, 13 Dec, 2023 at 9:29 PM

Download formcycle | Frontend-Server | Frontend-Server (Inbox) | Checksummen

Minor improvements

  • After a user has registered, they receive a welcome email with useful links. The welcome email can be activated or deactivated in the system settings.
  • Users are automatically deleted when a client is deleted; if the user is no longer used in any other client. This functionality can also be configured via the system settings and is enabled by default.
  • Unused users (users not assigned to any client) are highlighted in the user overview menu.
  • It is now possible to overwrite the robots meta tag in the meta area. This can be used, for example, if a form should not be recognized by search engines.
  • For widget plugins that offer form elements with select options, placeholders such as [%rate1.lsttxt%] can now also be used to access the display text of the selected option.
  • More than one "on-submit" callback can be registered using a new function. Previously, only a single callback could be registered, which was not usable by plugins or generic scripts, as that would overwrite the existing callback.
    • $.xutil.onSubmit(callback)
    • The callback receives a parameter of the type "OnSubmitCallbackData". This is an object with currently only one entry "submissionBlocked", which specifies whether the form is scheduled to be submitted after the callback was run.
    • The optional return value of the callback is of the type "OnSubmitCallbackResult". This is an object with a current optional entry "preventSubmission", which can be used to prevent the form submission.

Changes

  • The email action no longer throws a hard error if the email is sent to a user or a user group and the user does not have an email address. Instead, a soft error is produed and a corresponding warning is added to the protocol.
  • User group dependent conditions in the form designer (available-if, disabled-if) now use the UUID as a reference. This makes it possible to rename a user groups without removing the selected user group in the form designer.
  • When importing forms without the state "received", this state is created automatically.
  • When expired email verification links are opened, a new verification email is sent automatically.
  • All login services enabled for the backend are also available when opening a review link and the form record requires a login.
  • The Kerberos user filter ("ldap.override.filter.kerberos.user") was migrated from the "application.properties" file to "kerberos.properties" file.
  • Improved UI for the LDAP search in the Kerberos user filter configuration menu.

Fixes

  • The placeholder [%$USER.userName%] returns the user name of the formcycle profile, if available.
  • The placeholder [%$RECORD_ATTR%] works within form field properties, for example when used within the label of a form element in the form designer.
  • If a form placeholder is used within a form field property that allows HTML, the value of the placeholder is correctly HTML-encoded, so that the value is displayed correctly.
  • Reduction of the risk that certain (Chromium-based) browsers change the value of the hidden input field of the appointment finder via the autofill feature. This could result in incorrect appointment dates being displayed.
  • Files from repeated upload fields with the "automatic upload" option enabled are saved in the correct order.
  • An error no longer occurs when opening the designer for a form that lacks the system state "received".
  • If files from a repeated upload field are accessed in the workflow, the files are returned in the same order as they were submitted and are displayed when the form record is reopened.
  • When moving actions in the workflow designer that allow a file to be selected, an error no longer occurs if the action is moved to another processing chain.
  • Fixed an error when installing and unpacking plugins.
  • Fixed an error when a form record is submitted again via the inbox, which resulted to the incorrect message "Form not found".
  • No role permissions are required to access form records via the review link, which is the behavior as it was in version 7 of formcycle.
  • Minor UI bug fixes and adjustments.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article