As a form builder, I would like to allow a field to be visible, required or enabled, so that my form behaves dynamically depending on user responses.

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.0.0 M6
• Component/s: Forms
• Labels:
  • QA-AUTOMATION
  • S
  • boa
  • fw_test_poshi
• Epic Link: Form Rules
• Sprint: F&W #29 - Nov 07 - 18
• Git Pull Request: https://github.com/vicnate5/liferay-portal/pull/561

Goal:

• Allow the form builder to set a visibility condition to a field, so, depending on user response, that field would be shown or hidden;
• Allow the form builder to set a required condition to a field, so, depending on user response, that field would be mandatory for submission;
• Allow the form builder to set a enabled condition to a field, so, depending on user response, that field would be editable or read only;

Users:

• Form builder - persona in charge for building the forms and designing their behavior.

Benefits:

• Have a dynamic form that: only shows relevant fields, mark fiels as required and enable or disable fields to the user, according to his/her responses.

User Story:

As a form builder, I would like to allow a field to be visible, required or enabled, so that my form behaves dynamically depending on user responses.

DOD:

• Access the rules manager using the manage bar, by clicking the rule button;
• Interface support to apply rules;
• Implement functional tests for this feature;
• Create feature documentation.

Expected Product Behavior

Table of interaction with fields and rules (IF/DO)
https://docs.google.com/spreadsheets/d/1PrbgQQ81O-9Flv1ICUztnW0dKarVKUKGufjRSYgHFsM/edit#gid=127518355

Manage bar

• Undo and redo keep working;
• The second icon "Rules { }" is active;
• Users can save a Form with rule panel opened;
• If the Form Builder is creating or editing a rule and clicks on Save button, the Form understands that he/she needs to add the rule first and shows an alert (panel warning) to avoid the user to lose the rule information.

Condition Title > Switch "and" and "or"

• Is disabled if we have just one condition;
• If there is more than one condition, it turns into active mode.

Condition Card

• If there is more than one card, a kebab menu is activated for all the cards in the condition section and the user can delete the card using this menu;
• If there is just one card the kebab menu is not available.

Action Card

• If there is more than one card, a kebab menu is activated for all the cards in the action section and the user can delete the card using this menu;
• If there is just one card the kebab menu is not available.

Vertical Timeline

• The plus button below and aside the Condition section, adds a new Condition after the last one created;
• The plus button below and aside the Action section, adds a new Action after the last one created;
• All gray dots are milestones in the timeline.

"Add Rule" Button

• Adds a rule.
• After adding, the user turns back to the rule manager (Home screen);
• The recently added rule appears in the rule manager (Home screen).

"Cancel" Button

• If the user clicks on this button, it does not save the rule;
• After clicking, the user turns back to the rule manager (Home screen).

Product Design references:

• Forms 14 - Rule Show-Hide: https://invis.io/YG82DKMCU.

Functional test

• LRQA-28191