Release notes
Apr 01 2022
FORMCYCLE 7.0.12
Changes
- Update the included Spring framework dependency to the latest version. Previous version contain a version of the Spring framework that is vulnerable to CVE-2022-22965. Currently, we are not aware of any scenario where this vulnerability can be exploited. We still recommend you upgrade to the latest Xima® Formcycle version.
Checksums
Mar 22 2022
FORMCYCLE 7.0.11
Features
- Automatic uploads: When you open a form and select an upload, the file is only transmitted to the server when you submit the form. For larger files, this may take a long time. To alleviate long submission times, you can now enable the new automatic upload feature in the form designer. When enabled, files are uploaded in the background while you can continue to fill out the form. You can also interact with automatic uploads programmatically via xutil.ajaxUploadManager.
- Image compression for uploads: Images uploaded by users can end up large, such as when they take an image with their mobile phones. You can enable the new image compression feature in the form designer for upload elements. When enabled, uploaded images are compressed and scaled automatically. To save space, the original file is discarded.
Changes
- You can now add more than one form store URL in the Look & Feel menu in the backend. When you want to create a new form on the forms overview page, one option is displayed for each form store that lets you import forms from that store.
- At places where you can configure a database connection in the backend, a warning is now shown when no driver is installed for the selected database type.
- The inbox lets you select and run user-defined workflow event. Previously, the selection used the names of the workflow processing chain, which was confusing to some users. Now, the names of the user-defined events are displayed.
- Selecting CSS classes in the form designer: The form designer lets you choose and add CSS classes to a form element. Previously, you could only add CSS classes that were defined in an existing CSS file. Now, you can add any arbitrary CSS class, and classes from CSS files are offered as suggestions. In addition, you can now also add CSS classes to the container of a form element.
- Variables in the configured extension of an upload element are now replaced.
- The note warning users that they are using an outdated browser now shows up for all versions of Internet Explorer.
- New JavaScript functions were added that let you control the appointment picker programmatically: jQuery.fn.appointmentPicker
Bug fixes
- The inbox lets you filter form records by their subject again.
- The workflow action Date and time offers several pre-defined date formats. Some were incorrectly labeled, this has been corrected. Also, a few more pre-defined formats were added.
- Show the correct error message when submitting a form with an uploaded file that has a size of 0 bytes.
- Server validation is now correctly skipped when the submit button does not require the form to be validated. Note: this requires the settings Validate submit button to be enabled in the form designer.
- Variables in the default HTML response page are replaced, even when no explicit response page was set in the workflow.
- The variable section to the bottom of the form designer lets you add hidden variable input fields to the form. Variables within the default value of non server-only variables are now replaced.
- Visibility and read-only conditions are evaluated correctly for select elements with auto complete enabled, even when such an element is hidden or disabled initially.
- Text area elements with the option auto resize enabled adjust their size correctly even when such as element is initially hidden.
- All users can see and change the available states and user groups for state and user group based restrictions in the form designer.
- Minor bug fixes for the server validation feature.
- Minor UI fixes for the backend user interface.
Checksums
Feb 14 2022
FORMCYCLE 7.0.10
Changes
- The workflow event After state change is now triggered even when a state change action to the current state of the form record was executed.
- Saved form records or form records waiting for confirmation of a double opt-in are locked and now also do not reveal any information about the form record subject 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 restricted access to the file or deleted the file. This adjustment affects both the backend as well as frontend forms.
- Form records of offline forms can still be opened and submitted. See the access settings of a form that lets you configure this behavior.
- 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 directory for uploads in backend has been adjusted.
- Configuring custom CSS for the backend requires an appropriate 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 label 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.
- No more unnecessary redirection when opening 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 server-side button validation is disabled in the form designer. In old forms this is disabled by default, and when xf-action is accessed via JavaScript, you can now access the plain value again as in previous versions.
- Conditions are 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 form records can now be exported from the inbox.
- Fixed minor user interface bugs.
Checksums
Dec 20 2021
FORMCYCLE 7.0.9
Bug fixes
- Security fixes. Among others the used logging library was updated to the latest version. See here.
- Data sources used in selection elements are displayed correctly again in the element properties.
- Appointment calendars used in appointment finders are displayed correctly again in the element properties.
Checksums
Dec 15 2021
FORMCYCLE 7.0.8
Changes
- The used logging library has been updated to the latest version.
- Via application settings it can be specified whether information about the server should be transferred to the licensing system.
Bug fixes
- The default settings in the designer are saved correctly again.
- If there are multiple form elements with the same name then the JavaScript function getLabel() returns the label for each of the form elements.
Checksums
Dec 13 2021
FORMCYCLE 7.0.7
Changes
- XFC_METADATA.urls now includes request & requestBase:
- request: URL for a request to the current form with fragment and query parameter.
- requestBase: URL for a request to the current form without fragment and query parameter.
- Dates are specified with the Export as XML action with GMT time zone.
- Enhancement of plugin API for form resources.
- In Designer, a warning message appears if the web socket connection could not be established.
- Processing forms with plugin actions results in an error if the corresponding plugin has been uninstalled.
- Forms with invalid workflow are switched directly to maintenance mode after import / after update.
Bug fixes
- The logging library has been updated to the latest version to close a security hole.
- Unify the replacement of the variable [%lang%].
- The JavaScript function getLabel() returns exactly one label even for selection elements (in checkbox/radio button form).
- The error() and errorFunc() JavaScript functions can also be used to set errors for selection elements (in question form).
- System messages can be created, edited and deleted again.
- The responsive behavior of images has been improved.
- The state of form records with new workflow is taken into account during Excel/XML export.
- Commas no longer cause incorrect table structure when exporting forms to Excel.
- Formatting of text elements is applied correctly in the form.
- Automatic height adjustment of Textarea elements works even if the element is initially hidden.
- HTML response pages can be used with additional language variations.
- The HTML attribute aria-label is set correctly for fieldset and container elements.
- Performance of forms has been improved.
- Errors in evaluating the permission to create / edit forms have been fixed.
- Data sources and counters can be requested in the form via the corresponding URL also with frid as parameter.
- Fixed minor interface errors.
Checksums
Nov 04 2021
FORMCYCLE 7.0.6
Bug fixes
- The button action Send works correctly again on frontend servers.
- The button actions Submit no save and Submit popup not save are working correctly again.
- User defined events can be triggered correctly in the inbox again.
- The form store is now always displayed in the correct language.
Checksums
Nov 01 2021
FORMCYCLE 7.0.5
Features
- Preconfigured forms from various application areas can be easily installed and used via a form store.
- Forms can be tagged with filterable keywords.
- With the new permission Switch to any state, form records can be moved to any state, regardless of the access configuration to the state.
- In the settings of the workflow action Compress ZIP, a format can now be specified which determines the folder structure within the ZIP file.
Changes
- Form records in states of the new workflow are not accessible via the Processlink (variable: [%$FORM_PROCESS_LINK%]) by default. To make form records accessible to external access, this must be explicitly configured in the state settings.
- Forms with incorrect but disabled actions can be saved without switching the form to maintenance mode.
Bug-Fixes
- Performance issues with form validation have been fixed.
- Validation errors in the form are positioned correctly.
- Form record data is locked during complete processing. The processing lock can be removed in the inbox if needed.
- The provided HTML templates in the workflow action HTML response page are sorted alphabetically.
- The Inbox restriction when calling forms via the ProcessLink (variable: [%$FORM_PROCESS_LINK%]) takes effect correctly again for forms with old workflow.
- When updating a form with new workflow, errors no longer occur.
- The configured file name in the element settings of upload elements is also taken into account in the attachment overview of the inbox.
- Fix minor interface and translation errors.
Checksums
Oct 14 2021
FORMCYCLE 7.0.4
New system variables
- [%$CLIENT_MAIL_SENDER%]
- Returns the mail sender address of the client.
- [%$CLIENT_MAIL_SENDERNAME%]
- Returns the mail sender name of the client.
Both variables are used by default for the Email from and Sender name parameters, respectively, in new Email actions.
New application properties
- mail.smtp.connectiontimeout
- SMTP Socket connection timeout value in milliseconds.
- mail.smtp.timeout
- SMTP Socket I/O timeout value in milliseconds.
Bugfixes
- The use of multiple filters in form-specific inbox views works correctly again.
- The inbox editor role has all the subrights of the inbox super right by default.
- When creating a form with new workflow from a form with old workflow, the states and their references inside the form are inherited.
- Client-side performance of forms has been improved.
- Fixed some bugs in client-side validation & updating of forms.
- The JavaScript functions setRequired(...), setGroupReq(...), setMinValue(...) & setMaxValue(...) work correctly again and are applied to all selected form elements.
- The selection list of mandatory selection elements does not collapse again directly when the element is clicked.
- Form titles are no longer truncated on import.
- Form printing via the Print service no longer prints a gray line at the beginning of pages.
- When printing forms via the print service, the Mandatory fields hint is only printed if it is also enabled and the print service action does not suppress this.
- The Layout (CSS) of the form is also applied in the form preview.
- Text elements are displayed in the preview or live mode of the form exactly as they are in the form designer.
- The empty if hidden option of form elements works correctly again.
- Form elements with checkboxes that still have the checked option enabled can still disable this option. This option of checkboxes was removed in version 7.0.0.
- The action placeholder [%$<action name>.RESULT%] returns a JSON value, such as a map.
- Improved warning messages when importing forms with missing dependencies.
- Fixed a bug in the plugin interface ISearchTermHandler#triggerSearchTermNotExists.
- Deleting form versions no longer causes an error.
- Unnecessary error logs in the designer have been removed.
- Help links of endpoints in the workflow designer point to the correct help pages.
- Fixed minor UI errors.
check sums
Sep 16 2021
FORMCYCLE 7.0.3
Changes
- Performance optimization for database updates.
- The content type of the requests of the HTTP-Request action of the new workflow is application/x-www-form-urlencoded if no files are transferred. The content type is multipart/form-data when files are transferred or when the "Always use multipart request" option is enabled.
Bug fixes
- Forms from version 5 can be opened again without errors in the form designer.
- If URLs are removed from the Look & Feel settings, an error no longer occurs on the login page.
- JavaScript change events update the dependencies of question select elements. e.g. by $("[data-name=sel1]").trigger("change").
- The JavaScript function setDataType() is applied correctly.
- Fixed an error that could occur when updating a form version.
- Performance issues with nested conditions have been fixed.
- The POST-Request action of the old workflow works again as in version 6, i.e. the content type of the request is always multipart/form-data, unless "Do not transfer files (no multipart request)" is active. Then the Content-Type is application/x-www-form-urlencoded.
- Fix minor UI errors.