Data privacy notice

 

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

 

             

8.1.3

Modified on Fri, 9 Aug at 4:08 PM

Release date

  • July 8th, 2024


Download links


Fixes


Forms

  • When exporting forms, the display of available data sources, form files and templates is now provided with a scroll function for large element lists.
  • Even with an empty header prefix field of an OIDC login service with direct header authentication, the client is now initialized correctly.
  • When creating a new client with the client language 'German', the text for displaying the remaining characters in a text area has been adjusted to the new default value "x von y verbleibenden Zeichen".
  • The placeholder [%$USER.phone%] is no longer supported, only for LDAP and Kerberos logins it is preassigned from the telephoneNumber profile attribute.
  • After adding a new property to the form element widget, it is no longer necessary to restart the server to display it in the Form Designer.


Workflow

  • Workflow validation can now handle very long button names.
  • The Workflow Designer no longer displays a validation error if a form password has been configured for a workflow status.


Backend

  • If the authorization for the creation of an 'External user access' (login service) is missing, a tooltip now correctly informs about this.


Documentation

  • Incorrect links to the JQuery documentation in the Formcycle 8.1.2 help have been corrected in the Formcycle 8.1.3 help.



Changes


General changes

  • In the 'My forms' area and in the system settings (System settings -> Look & Feel -> Links), the name "Form store" has been replaced by "formcycle.STORE".


Forms

  • The validation of variable names has been corrected so that some special characters such as underscore are now allowed again.
  • The placeholder [%$USER.phone%] is no longer supported. To access a user's phone number, the corresponding attribute in [%$USER.rawData%] must now be used (e.g. [%$USER.rawData.telephoneNumber%] for LDAP).



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