FORMCYCLE 7.0.10


Feb 02 2022

This blog post is not published yet.

Download 7.0.10

After installing this version it is necessary to perform a database update in FORMCYCLE.

Changes

  • The workflow event After state change is now executed even if a task is in the selected state for the selected amount of time without the state having changed.
  • Cached form records or form records waiting for confirmation of a Double-opt-in process are locked and now also do not reveal any information about the record title or process ID. These records are also no longer exportable.
  • If files are uploaded that cannot be read, a corresponding error message is displayed. This can happen, for example, if a virus scanner has locked or deleted the file. This customization affects both the backend and frontend forms.
  • Form records of offline forms can still be called and submitted. There are new configuration options for this under the access configuration of the form.
  • The Quartz scheduler can be configured via application settings. The following parameters can now be customized:
    • The number of threads in the thread pool.
    • The time for re-executing triggers.
    • The time until a trigger is considered to have failed.
  • The name of upload elements was previously limited to 100. The name can now be up to 255 characters long.
  • The default value for the number of connection attempts to the frontend server has been increased to 50.
  • Temporary location for uploads in backend has been adjusted.
  • Configuration of custom CSS for the backend requires activation via license.
  • Improved log messages when the form record limit is reached.

Bug fixes

  • Security improvementS. Among other things, the logging library used has been updated to the latest version. See also here.
  • Error messages that occur during server-side validation are now correctly displayed for repeated elements
  • Filtering by keywords in the form overview also works with numeric values as keywords.
  • Fixed an error when deleting elements from repeated upload elements. Files are also no longer lost when resubmitting the form.
  • Fixed an error when determining the content type and character encoding for the HTML response page and HTTP request actions.
  • The color of links, such as in the lead text of elements, is no longer overridden and can also be adjusted via CSS.
  • When W3C compliant mode is disabled, the HTML attribute name is still set for containersand fieldsets.
  • Also for Fieldset & Container elements, the HTML attribute data-org-name or org-name (when W3C compliant mode is disabled) is set.
  • When cleaning file names in file-generating actions, characters before the last slash are no longer truncated.
  • Unnecessary redirection no longer occurs when calling forms without access restrictions.
  • URL parameters are preserved when redirecting within a form session.
  • When sending form invitations, the form-specific inbox view is updated.
  • Fixed an error in the workflow designer that could prevent it from opening.
  • The tile for importing forms from the form store is not displayed if no URL for a form store has been set in the system.
  • Fixed an error when importing forms with KERBEROS access.
  • Hidden form elements are excluded during server-side validation. Conditional visibility is now also taken into account.
  • The value of xf-action is no longer encoded if the setting for server-side validation of buttons is disabled in the form designer. In old forms this is disabled by default, if the xf-action is accessed here via JavaScript, you now get the non-coded value again.
  • Visibility conditions are also evaluated correctly for image elements.
  • Form variables, which are used in the form, are now also replaced during redisplay. In addition, system variables in the Identifier for duplicate data sets are also replaced correctly.
  • If the number of repetitions of a form element is negative, this value is treated as 0.
  • Errors in server-side validation of repeated form elements are now displayed.
  • When using FORMCYCLE with a Microsoft SQL Server database, more than 2100 operations can now be exported from the inbox.
  • Fixed minor user interface bugs.

Checksums