Dynamic Form Features OverviewLast Updated: 07/15/2016 Introduced in Verision: 2.0 |
There are numerous ways in which Form Designer can make the Form dynamic in Decisions 3.2. In other words, it is possible to change Form Components, Visibility, and Behavior based on Form Input Data and Form Rules.
This document overviews the variety of such possibilities.
In the Form Designer we locate Form Configurations first. This can be done by Navigating to the Form Designer Explorer, selecting Surface, and clicking Properties.
The first section that is helpful to add dynamic to the Form is Form Data. Here, we can define any Data for the Form input which can be used by Form Components. In this way we define Variables of desirable Type and we will have to populate them with Values from the Flow. To learn more about Form Input data please refer this document.
Next section that is used to add dynamic to our Form is Form Rules. It is found under Form Data section in the Form configurations that we overview in this tutorial. This section has four blocks: Data Flows, Visibility Rules, Validation Rules, and Outcome Rule Groups.
Data Flows.
In Data Flows section we can make our Form dynamic by using an existing Flow. For instance, we can send user input from our Form (textbox, list selection, etc.) to the Flow, then do some work with this data in the Flow, and populate our Form components with the data that our Flow outputs. To learn more about Data Flows please refer this document.
Visibility Rules.
With Visibility Rules we can use Decisions Rule Engine to dynamically decide what Form components should be visible. For example, we can send data from the Form control to the existing Rule and based on the Rule evaluation decide which Form components should be visible. To learn more about Visibility Rules please refer this document.
Validation Rules.
To ensure that a user enters valid data in a form’s required fields, you can configure a form to run validation rules. The rules can run upon submission of the form, upon a field losing focus (i.e. the user clicking out of a field), or upon startup of the form. The startup method of executing a validation rule displays alerts next to the fields when the form first loads. This can be useful for highlighting form fields that must be changed because their default values, or values inherited from a preceding step, are invalid. To learn more about Validation Rules please refer this document.
Outcome Rule Groups.
It is possible to create a custom Rule that can be used to control Form’s Outcome behavior. For instance, we can use data Form controls to pass it to the custom Rule. Then, depending on Rule evaluation we can create Form Outcome path and do some work in the Flow (like Send Email or open another Form). To learn more about Outcome Rule Groups please refer this document.
Next, each Form component can be controlled dynamically with Flow Data. We can configure to Enable/Disable component or mace it Visible/Invisible depending on the Boolean Flow Data that is sent to the Form. To learn more about Form Components Behavior please refer this document.
Finally, we can add dynamic to our Form by using Flow Data that is available for the Form Step. We can create Labels with Flow Variable names or values. To read more about this way of adding dynamic to the Form please refer this document.
