Type: Regression Bug
Affects Version/s: 7.2.10 DXP GA1, 7.2.X, Master
Backported to Branch:Committed
Sprint:Forms_7.3_20, Forms_7.3_21, Forms_7.3_22, Forms_7.3_23
Git Pull Request:
Rule execution fails in certain circumstances, particularly when multiple rules are required to perform actions on the same fields or groups of fields.
As a Forms Designer I need to create a form that uses a "Select from List" or "Single Selection" to enable the Forms Submitter to select whether 1, 2, 3 (or more) sets of fields are displayed. This should be able to be accomplished with multiple rules as follows:
- If "select from list" = "1" then show first set of fields
- If "select from list" = "2" then show first and second set of fields
- If "select from list" = "3" then show first, second and third sets of fields
- And so on... (and if "0" don't show anything)
The business scenario in this case is as follows:
The form is a "School Enrolment" form, allowing a Parent to apply to send their child to school. The question being asked is "How many siblings (brothers or sisters) does your child have?", which will require the parent to enter First Name, Last Name, Date of Birth and Gender for each sibling. If they answer "0" to the question, then no fields should be displayed. If they answer "1" they should be able to fill in the details for that one sibling, "2" for two, "3" for three and so on.
Form Submitter sees the appropriate number of sets of fields based on their selection
It appears that only the final rule (in the above example, "3") is executed, otherwise no fields are displayed at all - i.e. if the user selects "3" then three sets of fields are displayed, if they select any other option then no fields are displayed at all.
One "select from list" field (or "single selection" - behaviour is identical) with options defined for 0, 1, 2, and 3. Label "How many siblings does your child have?", name "HowManySiblingsDoesYourChildHave"
"First Name", "Last Name", "Date of Birth" and "Gender" fields (Text, Text, Date, Single Selection) named FirstName1, FirstName2, FirstName3, LastName1, LastName2, LastName3, DateOfBirth1, DateOfBirth2, DateOfBirth3, Gender1, Gender2, Gender3
(In addition to the described bug, this UX is not helpful as it is not clear for the Form Designer which fields have been selected when the field labels need to be non-unique)