News

26 posts

May 11 2023

Fixes

Fixed an error when sending mails via the system mail server. Once the system mail server settings were saved once, mails could not be sent anymore, and a server restart was required.
Permissions when writing files to the file system are also inherited properly now when the old workflow is used.
Fixed an error when updating a form. The error occurred when the uploaded form contained a workflow version with the same technical ID as an existing version.
Options for select elements from plugin catalogs are not extended with the default options anymore. For example, when a select field had two options, the third default option with the name "option 3" was added.

Checksummen

Posted by Release Notes · Categories: News, Release Note · Permalink

Posted in

Apr 17 2023

Fixes (web forms)

Empty formula conditions do not result in a script error anymore. Empty conditions are treated as "true".
Improved performance for formula conditions.
Form elements hidden via conditions are not shown anymore when the media type is set to "print".
When a form element is initially hidden and has the option "clear if hidden" enabled, existing values are now cleared again.
When a form element is disabled by a condition, validation error messages are removed if any were present.
Improved error message when a file was uploaded that exceeds the upload limit which was configured via System -> General.
Fixed an error that occurred when FORMCYCLE was running on a Windows server and a file with a colon in the file name was uploaded.

Fixes (backend)

The workflow section in the generated form overview PDF is displayed correctly again.
More resilient reconnection attempts when the connection to a frontend server was lost.
Fixed an error in the inbox when the subject of a form record contained special control characters such as U+0002.

Checksummen

Posted by Release Notes · Categories: News, Release Note · Permalink

Posted in

Mar 28 2023

Changes

Increased the character count limit for the description of an appointment template

Fixes

When creating new directories via the workflow action "Save to file system", permissions from the parent directory are inherited correctly again.
Fixed an error when sending forms via the offline plugin.

Checksummen

Posted by Release Notes · Categories: News, Release Note · Permalink

Posted in

Feb 20 2023

Features

Backend

Previously, you could already use certain types of placeholders in database and LDAP queries. Now you can also make use of user placeholders such as [%USER.id%] or [%LAST_USER.id%]. If a database or LDAP query is initiated via AJAX from a web form, it is important to send the current ID of the form session via the frid parameter for this to work. The code editor offers a code template for database and LDAP queries which already contains this parameter.
In the appointment management menu, you can now enter a custom subject and description, which is used for the events in the ICAL calendar file for an appointment. You can also enter placeholders or I18N variables.

Form designer

When you choose a data source (e.g. database or LDAP query) for the options of a select element, you can now also configure a column for the title of each option, in addition to the display label and value of the option. When the select element is displayed as a list of checkboxes or radio buttons, the title is shown to the user when they hover over an option with the mouse.
In previous FORMCYCLE versions, the values of all columns from a data source were always added to the select element as data attributes (e.g. data-col0, data-col1). Now you can deactivate this behavior so that such attributes are not generated any longer. This may be useful in case the data source contains sensitive data you do not want to make public.

Changes

Backend

For each appointment, you can enable the ICAL URL which contains all booked appointments and can be imported into mail clients or calendar applications. This ICAL calendar now includes the fields X-PUBLISHED-TTL and REFRESH-INTERVAL. This makes it easier for mail programs and calendar applications to decide how often they should check for updates. Currently, this value is set to 1 hour.
The menu System -> Server information now also list the malware scan directory, which is used to store uploaded files temporarily when the system performs a malware scan.

Workflow

Due to security concerns, merge fields are not interpreted as HTML anymore when using the workflow action "Word Fill". If HTML is required, use the Word function "html" explicitly, e.g. "tf1.html()".

Form designer

When you add a condition to a form element (e.g. hidden-if), you can already enter a custom formula such as [%tf1%] == "Test". Starting with FORMCYCLE 7.4.0, this formula can now access the JQuery instance of the current element via the this context. This is especially useful for repeated elements, when you want to access the current element repetition or another element within the same repeated container. For example, if both tf1 and sel1 are form fields within a repeated container fs1, then you can use the formula this.closest(".dynamic-row").find("[data-org-name='sel1']").val() === "5" for tf1 in order to check whether the corresponding select field from the repeated container sel1 has a value equal to 5.

Fixes

Backend

Form export files with a manually created state that was named Received can now be imported correctly again.
Various small bug fixes and security improvements. In particular, used libraries were updated for this purpose.

Frontend forms

External users from an OpenID Connect identity provider can now log in to web forms again even when they open the form on a frontend server.
The automatic upload feature for upload elements works correctly again even when forms are integrated via AJAX into a third-party page.
When a form contains an appointment picker and server-side validation was enabled for any element, the selected appointment got cleared in case the form was submitted with invalid data and the server rejected the form submission. This has been fixed so that the selected appointment now remains selected.
When an element is repeated, you can defined a repeat trigger such as a text field that controls the number of repetition. When a new repetition is added, the value of the repeat trigger text field is updated, and vice-versa: When a different number is entered in the repeat trigger field, new repetitions are added or existing repetitions are removed to reflect the new value of the repeat trigger. In the first case, when new repetitions were added, the initial state of conditions such as hidden-if for the new repetition were sometimes not evaluated correctly.
Affects select elements for which the autocomplete option is enabled:
- FORMCYCLE generates an <input> element in addition to the <select> element. The name of the <input> element contains the suffix _autocomplete. (e.g. sel1_autocomplete), but the data-name attribute did not. This was fixed so that the data-name now also contains the derived name with the suffix.
- Since FORMCYCLE 7.0., when a condition references an autocomplete element, the entered text of the input field was erroneously used instead of the option value. For forms in multiple languages, this could not work. This was fixed so that the option value is now used. To preserve backwards compatibility, a new option was added to the form designer that can be found in the properties panel to the right, at the bottom of the Form tab in the advanced section: Use option text for conditions referencing an autocomplete element. For existing forms, this option is enabled; for new forms, this option is disabled. We recommend that you keep this option disabled and do not enable it.

Form designer

Fixed a bug where the CSS classes of the most recently selected element was applied to all selected elements. This bug only occurred when multiple elements were selected at the same time.
The setting for the W3C compliant mode now defaults to disabled for old forms again. It is still enabled by default for new forms.

Workflow

The dialog for loading unsaved changes is now closed again after you press a button.
When executing an HTTP request action and the server responds with a redirect (HTTP header: Redirect) and the redirect is a relative URL, that URL is now resolved against the request URL. This is correct as specified by RFC 7231. Previously the URL was not resolved at all.
- There is also a new option that lets you choose how to resolve relative URLs: against the request URL, against a custom URL, or not at all.

For plugin developers

You can now access the data of the current form request session ("FRQSession" ) within plugins of type IPluginFormPreRender, IPluginFormPrePersist, IPluginFormPreProcess, IPluginFormPreResponse as well as in workflow action plugins and possibly also placeholder plugins. Furthermore, you can also write values back to the FRQ session via the return value of IPluginFormPreRender, IPluginFormPrePersist, IPluginFormPreProcess, IPluginFormPreResponse, and workflow action plugins.
Plugins of type IPluginFormPreRender are usually only executed when a form is opened via the /form/provide URL. Now you can opt-in to have your plugin get executed in other situations as well, such as when opening a form in the inbox or when printing a form via a print services. To do so, override the shouldExecute method of the IPluginFormPreRender plugin.
Various libraries have been updated

Checksums

Posted by Release Notes · Categories: News, Release Note · Permalink

Posted in

Jan 23 2023

Features

Support for sending emails via via the Microsoft Graph API. This lets you use Microsoft Office 365 accounts for the email server configuration. See system email server and client settings
Added a new URL parameter jsonPath to data query URLs (CSV, XML, JSON, database, and LDAP data sources). These URLs all return a JSON object with the requested data. When a jsonPath is given, only the data at that JSON path is returned. This makes it easier to filter for the data which you want to retrieve.
The form designer lets you configure whether a form element is available or not, depending on the form record's state the user's user group. When it is not available, the value of that element is not shown in the data table in the inbox. A new role permission was added that lets you configure this behavior. When a user was granted that permission, they can see the values of all form elements, regardless of whether they are available.

Changes

Improved support for direct authentication methods for forms (e.g. via header parameters):
- When the user open a form, an attempt to authenticate the user is made once for each configured direct authentication method.
- In case neither direct authentication was successful, and if at least one indirect authentication method (e.g. system login) was configured, the login prompt is shown to the user.
- In case neither direct authentication was successful, and no indirect authentication methods were configured, the HTML template Login failed is shown to the user.
Replace the existing XSLT engine with a newer engine. The new engine now also supports XSLT 3.0, XPath 3.1 and XQuery 3.1. Because the XSL parser of this engine works a bit stricter than the old engine, small incompatibilities with wrong XSLT may be possible. An overview of known errors can be found under XSL transformation
Rework the mail server configuration and mail server placeholders:
- As the system administrator, you can allow each client to, or prevent them from making use of the system mail server.
- As the system administrator, you can allow each client to, or prevent them from configuring a custom client mail server.
- The default values form the system mail server for the sender address and the sender name can now also be changed by each client.
- The placeholders [%$CLIENT_MAIL_SENDER%] and [%$CLIENT_MAIL_SENDERNAME%] are now deprecated. You should use the placeholders [%$DEFAULT_MAIL_SENDER%] and [%$DEFAULT_MAIL_SENDERNAME%] instead. The deprecate placeholders are still replaced, but should not be used anymore.
- When neither a client nor a system mail server was configured, or the system mail server cannot be used, workflow actions that require a mail server are not available anymore.

Fixes

Frontend forms

Fixed an error with disabled fields when an existing form record is opened again.
Fixed an error when multiple JavaScript files are concatenated if a form is opened with inline mode enabled (URL parameter xfc-rp-inline=true).
Forms which require a direct authentication (e.g. via a header parameter) are now displayed correctly again.
The appropriate error template is now shown again when a form requires authentication via Kerberos and that authentication failed.
Fixed an error with visible-if conditions when the element is also repeated.
Fixed an error with the login process when the form was embedded in an external page via AJAX and a login service with popups was used.

Form designer

Allow the data-force-validation attribute in the form preview within the designer.
Better error handling for invalid autonumeric attributes when opening a form.

Workflow

Fix an incompatibility with the workflow action "Process log as PDF" where the action from existing forms was sometimes not recognized.
Fix a rendering error when printing a web form. A printed form sometimes contained tall empty sections when invisible containers were used.
Fix a bug in the Word fill action. When a PDF was using hidden Word controls, the base64img function did sometimes not insert the image correctly.

Inbox

Fix localization for the event status of when using the iCAL URL for an appointment configuration.
Remove the limit on the number of characters in form specific inbox views.
When you change the subject template form record, all form records are update. This update no longer fails when the subject of single form record could not be update. All other form records will still get updated now, and an error message is displayed at the end.
Values from question elements are now shown properly in the inbox; and are also included in Excel and XML exports.

Checksums

Posted by Release Notes · Categories: News, Release Note · Permalink

Posted in

Oct 27 2022

Features

Two new action for converting between files, base64 strings, and data URIs. This can be helpful e.g. when you want to embed images into a document as a data URI.
- See the actions Decode Base64 and Encode Base64
You can now set the HTTP headers Content-Security-Policy and Content-Security-Policy-Report-Only via System, General. It is possible to set different headers for the frontend and the backend.

Changes

You can now directly change the name, tags, description and group of a form when you import a form into Xima® Formcycle.
Reduce verbosity of protocol entries for soft errors when a file could not be resolved in the workflow.
It is possible to send automatic emails when the system is updated. When an update is started, but the system is already up-to-date, a different email with an appropriate text is now sent.
The PDF importer now lets you change the text of checkboxes and radio buttons before you import the form element into the form.

Fixes

Frontend-Formulare

Buttons that are disabled do not get enabled anymore after the form was submitted
Improved keep alive mechanism for form session.
The generated script for embedding forms via the API now also works in the header of a web page.

Form designer

Auto completion for the CSS classes in the form designer now works again for all available classes.
Fixed minor error with the presentation of the form within the form designer (relative URLs from @font-face rules are again resolved against the proper base URL)
Changes in the rich text editors are now applied faster.
When the builtin resource 031-extended-min.css is overloaded, this overload is now also respected within the form designer, so that the form looks the same in the designer.

Workflow

When you use the action PDF fill to fill PDF documents that conform to the PDF/UA standard, the resulting PDF document also conforms to the PDF/UA standard.

Inbox

Exporting selected form records as Excel or XML document is now possible again.
Fixed a performance issue with many form records in the inbox.
Booked appointments in the calendar view of the inbox are shown with colors again.

Backend

Update Dutch translations.
Small UI fixes in the backend and the designer.
Update the dependency commons-text to 1.10, due to the potential vulnerability CVE-2022-42889.
Improved security for the form designer and the backend in general.

For plugin developers

Authenticator plugins (IPluginAuthenticatorType) can now supply a custom UI for the external users configuration in the backend.
When a IPluginCallbackLogic plugin is used, the default allback logic is not executed anymore, only the callback logic of the plugin.

Checksums

Posted by Release Notes · Categories: News, Release Note · Permalink

Posted in

Sep 26 2022

Features

Form designer

PDF importer
- You can now open a PDF document in the form designer. This opens the PDF importer, which lets you copy form fields and texts from the PDF to the Xima® Formcycle form. The importer also offers several convenience features to help you with the conversion of PDF forms to web forms.
New form element Invisible Container
- The invisible container is similar to the standard container element. The main difference is that by default, the invisible container does not have a padding on each corner. In other words, you can nest as many invisible containers as you want to group elements without that having an effect on the visual appearance of the form.
- If you are using the Leitfaden plugin, you should update it to the current version. The invisible container element from the plugins is replaced by the built-in invisible container from Xima® Formcycle.
Enter custom formulas for conditions in the form designer
- Previously, form field conditions such required-if or visible-if only let you select a single form element with a value to check. Now, you can also enter a custom formula that may contain references to multiple form elements.
- The formula must be a valid JavaScript expression (and not a statement). You can use variables such as [%tf1%] to easily reference the values of form fields.
- Note: Custom formulas are incompatible with server validation. Even if server validation is enabled, custom formulas are not validated by the server, submitted data will be accepted at face value.
Free text input for select elements with auto complete
- A select element displayed as a combo box offers you the option to enable auto complete. Auto complete lets the user enter text and suggests available options depending on the entered text. Available options are validates, the user cannot enter text that does not correspond to an available options.
- This release adds a new option to select elements that allows the user to enter arbitrary text, even if that text does not correspond to an existing option.

Workflow designer

New workflow action Create protocol entry
- This action lets you create protocol entries for the form record with a custom message. These protocol entries can be viewed in the history tab of the inbox.
New workflow action Form record history as PDF
- This action lets you create a PDF document with the history of a form record as it can be seen in the history tab of the inbox.
Free content selection for the HTTP request action
- Until now, the HTTP request action only let you send requests where the body was either URL encoded (application/x-www-form-urlencoded) or a multipart body (multipart/form-data).
- Now you can either freely enter plain text or select a binary data for the request body content. You can also use this feature, for example, to interact with a JSON based REST API.

Changes

The license details in the license menu now also include a note about whether the Azure AD and WebDAV features are enabled.
Email notifications regarding failed system updates are now sent with their priority set to High.
Changes to the WebDAV connections menu:
- Modifications made to WebDAV connections (creating a new connection, editing or deleting an existing connection) are now logged in the client protocol.
- WebDAV connections cannot be deleted anymore when they are still used by the workflow of an existing form.
When a proxy server was configured in the JVM (Java runtime environment), that proxy server is used when sending emails via the email action, unless a different proxy server was configured explicitly.
- You can disable this behavior via the application property defaults.http.use_system_properties.
Removed the option that was added in version 7.1, which let you output the select options of select elements in multiple columns when creating a Word export. In order to position the select option in multiple columns, an additional table was created in the Word document, which interfered with Word functions such as rmt(), as those would affect the additional table with the select options, not the surrounding table as they did previously.

Fixes

Backend

Fixed file downloads in various menus in the backend. Downloading a PDF or Word export in Firefox does not result in a popup warning anymore.
You can now use more than one reply to address again in the email action. Also fixed the email body type selection.
Issues when deleting planned timed events of form copies were fixed.
Invalid application sessions do not prevent new logins anymore.
Form record from forms that make use of widget plugins can now be opened on the inbox frontend server again.
Due to backwards compatibility, the no-argument usage sel1.con() of the Word function con nows gets interpreted as sel1.con(""), and checks whether one of the field values is empty. This is for legacy support only, we recommend that for newly created Word documents, you always use quotation marks to avoid ambiguity.
- Additionally, you can now also use the new Word function sel1.empty(). It lets you check whether there are either no values or one of the values is empty. We recommend you use this function for select elements to check whether no or an empty value was selected.
Minor UI fixes in backend menus.

Form designer

Fixed issues when searching for form elements in the form designer.
Fixed minor issues with how the form was displayed within the form designer and how CSS was loaded. There are also new versions of some widget plugins that should be installed, such as for the Google reCAPTCHA Plugin.
When switching from a custom CSS theme to the defaul theme, that theme is now applied immediately to the form in the form designer.
The form preview now also supports privacy policies or imprints hat are configured to be shown as a dialog.
All available CSS classes are now suggested again when entering the CSS classes for a form element.

Frontend forms

When a form made use of upload fields with the automatic upload features enabled and also had a button with the action Submit no save, it was not possible to submit the form again after the submit button was clicked once. This is now fixed.
The client-side validations is now performed always performed, even when a form had a button with the action Submit no save and is submitted multiple times.
The marker that indicates whether a form field is a required field is now always set correctly, even when required-if conditions are combined with element repetitions.

For plugin developers

Added a new plugin interface: IPluginAuthenticationLogic. The existing plugin interface IPluginAuthenticatorType only works for form authentications that are done before the form is opened. Once authenticated, the user is always redirected to the requested form. This new plugin interface lets you define your own authentication logic, including custom redirections. For example, you could use this to implement custom login buttons for forms.
The plugin IPluginAuthenticatorType now also allows direct clients to be used, which authenticate the user directly without redirecting to a page from the identity provider. This allows you, for example, to implement a custom authentication via HTTP request headers.
Updates Pac4J to version 5.5.0. You should check authentication plugins that make use of the Pac4J API and adjust them if required.

Checksums

Posted by Release Notes · Categories: News, Release Note · Permalink

Posted in

Sep 08 2022

Fixes

Fixes a bug that sometimes resulted in the content of the JavaScript, CSS and meta section in the form designer being deleted.
The content of the versions menu with the workflow and form versions is loaded correctly again.

Checksums

Posted by Release Notes · Categories: News, Release Note · Permalink

Posted in

Aug 23 2022

Features

Support for WebDAV.
- This feature requires an appropriate license.
- The new backend menu Data, WebDAV connection lets you set up connections to a WebDAV server.
- The new workflow action Save to WebDAV server lets you transmit files to another system via the WebDAV protocol.
New switch condition added to the workflow.
- Use the switch action to check a value against many multiple cases. For each case, you can then run different actions. Compared with existing yes/no conditions, the switch makes your workflow easier to read, especially when you have many cases. For example, if you have a select field selMartialStatus, you can use the switch condition to test the value against the possible options single, married, divorced, widowed, in a partnership.
Automatic database and system updates when launching Xima® Formcycle
- Xima® Formcycle can now run all requires updates when it is started, so that you do not have to run a manual update anymore via the backend. This reduces the time it takes to update the system, and helps to avoid down times.
- For new installations, this feature is enabled by default.
- For existing installations, you can enable this feature in the backend via the menu System, Database.
Login via Azure AD
- The backend menu External users (authenticators) now lets you retrieve users from an Azure AD.
URL for monitoring the frontend server status
- Use the URL https://<domain>/<context>/monitor/fs/connection?name=MyFrontendServer to check whether the master is connected to a certain frontend server. You can also trigger a reconnection when the server is not connected.
- Due to security concerns, this URL is disabled by default. To enable it, you need to configure the application properties monitoring.enabled and monitoring.allowed.hosts.
Support for internationalized email addresses and UTF-8 headers
- Xima® Formcycle can now send emails to internationalized email addresses such as 山田太郎＠株式.会社, provided the email server supports it.
- To enable support for internationalized email addresses, go to the system or client mail server settings and enable the option Server suppports UTF-8 message headers (RFC6532).

Changes

Backend

To avoid issues when migrating data between different database systems, Xima® Formcycle now always treats all names case insensitiv. For example, when you have a client file named demo.txt, you cannot create a new file named Demo.txt anymore, even if your database supports it. No migration is required for existing systems that make use of such names. However, on the long term, we recommend you avoid these kind of name conflicts.
Fixes issues with downloading forms from password protected form stores. Also, the form store is now always displayed in the correct language.
If the hardware ID of a server has changed, when you attempt to update the license via the license menu page, a dialog shows up that lets you choose whether you want to register a new hardware ID or overwrite an existing one.
You can now use callback links with URL parameters for external users (authenticator). This may be necessary when the identity provider does not allow URL parameters in the callback URL.

Inbox

Previously, the inbox had only a predefined filter to display form records that arrived latest. It is now possible to filter form records to any modification range.
The appointment view of the inbox now displays appointments faded out, when they belong to form records that are either saved or are waiting for a double opt-in.
Improved the syntax of word fill functions. Parameters should now be enclosed in quotation marks. This lets you use arbitrary characters, including special characters. For example: selTrainPass.cb("1. class") oder selBookTitle.cb("The Final Odyssey is \"Comet Cowboy\"")

Workflow

The actions Create text file and Export as XML now let you access the content of the created files via variables.
The POST request of the old workflow now lets you add custom headers as well.

Frontend forms

JQuery and JQuery UI were updated to the current version.
The function $.xutil._load now also restores the number of element repetitions as well as the values of repeated elements.
The data type email for input fields does not allow a dot at the end of email addresses anymore. Domain names may end on a dot to indicate that it is a fully qualified domain name. However, in practice, many common email providers do not allow such email addresses.

Form designer

In the form designer it is possible to define for each form field in which status and for which user groups it should be available. If a form field is not available, the values are no longer displayed in the data table of the inbox anymore.
You can now select the number of print export columns for select elements. You can find this option in the form designer in the tab Advanced (at the bottom in the panel Word and PDF export). When the number of columns is set to a value greater than 1, the select options are placed next to each other in columns when you create a Word or PDF export.

Fixes

Backend

In full screen mode of the rich text editor, the button for the placeholder dialogue now works again.
When you download a file in the backend, now always in a new browser tab to avoid losing the currently opened page.
Several minor UI fixes.

Inbox

Web Content Accessibility Guidelines (WCAG) conformity in the inbox has been improved.
If there are multiple values for a form field, that values are all displayed in the data table of the inbox.

Workflow

If an unhandled exception occurs in the new workflow, the error page now always appears. It doesn't matter that another response page has been defined in an action that has already been executed.
LDAP workflow actions that use an existingLDAP query are executed correctly again.
Fixed an issue where filling a form field in a Word document filling a form field in a Word document was sometimes not possible.

Frontend forms

The session ID is now correctly forwarded when saving temporarily. In the case of forms with login, it was previously necessary to log in again after saving the form.
The conformity of web forms to the German accessibility guidelines (Verordnung zur Schaffung barrierefreier Informationstechnik) has been improved..

Form designer

The Word and PDF export feature now generates the correct Word function for creating checkboxes if used within repeated containers.
Form fields can have conditions that control whether they are visible, required, or editable. Such a condition may also reference a hidden variable field. Server validation now validates such conditions correctly as well.
If own HTML is entered in the rich text editor via the source code view in the form designer, this is now kept as far as possible and no longer cleaned up.
Improvement regarding false positives in relation to bot detection.

For plugin developers

PrimeFaces was update to version 11.
- Adjustments may be required for plugin with a custom UI.
- See the PrimeFaces migration guide for more details: 8 10, 10 11
- Some changes have been made especially to the Datatable component.
Updated pac4j. Plugins that provide custom authenticators should be checked and may required adjustments.
The builtin class PluginServletActionRetVal for the return value of servlet action plugin now contains constructors for all available parameters. Use of a custom implemenation of IPluginServletActionRetVal should be avoided, since these custom classes may not be available when communicating with a frontend server.
The form preview in the form designer is now placed inside a shadow root. This improves the encapsulation of the designer CSS and the form CSS, and prevents custom form CSS from affecting the layout of the designer.
- As a consequence, widget plugins now also need to separate their CSS.
  - IPluginFormElementWidget#getCssData has to return only the CSS required for the form layout.
  - IPluginFormElementWidget#getCssDataForDesignerUi has to return only the CSS that is needed to style the form designer UI.
  - @font-face rules need to be added outside the shadow root, not all browsers support @font-face within a shadow root yet (e.g. chromium)
- In addition, due to the shadow root, it is no longer possible to directly select elements in the form, starting at document context. If a widget plugin contains custom JavaScript for the designer that selects elements within the form preview, the JavaScript needs to be adjusted.
  - The function IFormDesigner.getFormDesignPanel() can be used to access the element in which the form is located. Inside this element, it is now possible to search for child elements in the form. For example:

import { instance } from "@de-xima/fc-form-designer";

function main() {
// Instead of selecting elements directly from the global scope
$(".XTextField");

// Select elements starting from the form design panel
instance().getFormDesignPanel().find(".XTextField");
}

Checksummen

Posted by Release Notes · Categories: News, Release Note · Permalink

Posted in

Jul 19 2022

FORMCYCLE 7.0.16

Download 7.0.16

Fixes

It is possible to use text templates within the form for the privacy policy or the imprint. In some cases invalid HTML was generated which could not be displayed by some browsers and also prevent certain plugins from working, such as the language switch plugin.
When the privacy policy or the imprint was shown as a link that opens a dialog, when the user clicked on the link the occasionally got reloaded.
Some form element conditions such as "hidden if" let you clear the form field when it is hidden. When combined with repeated form elements, this resulted in the internal form field "*_dyn_size" getting cleared as well. When the form element was set to not be editable after the first submission, this could lead to data loss.
Forms contains a form element with a "editable if" or "disabled if" condition could not be submitted anymore. This is now possible again.
When reopening forms with a repeated appointment picker, all selected appointments are displayed correctly now.