-
Type:
Story
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Component/s: Forms
-
Labels:
-
Epic Link:
-
Sprint:Forms #35 - Jan, 30 - Feb, 10, Forms #36 - Feb, 13 - Mar 03, Forms #37 - Mar 06 - 17, Forms #38 - Mar 20 - 31
-
Git Pull Request:
Goal:
- Remove from the action menu the "from" used to specify the origin page while setting the "jump to page" rule.
Users:
- Form builder
Benefits:
- Avoid user mistakes;
- Dicrease user efforts, reducing the steps and number of clicks to create a "jump to page" rule.
- Avoid inconsistent interaction to create a logic to "jump to page" rule.
User Story:
As form builder, I would just like to set the destination page (to) and do not worry about to set the origin (from) in the rule's action.
DOD:
1. The user should be able to set a target (and not a number of skiped pages);
2. The user does not need to define the "From" page, just the "To" page;
3. The "From" page will be automatically specified and not displayed on the interface;
4. The "From" page will always be the last page involved in the condition;
5. Confirmation Page should always be displayed on the Select field's page list (to);
6. If the same page is selected in rule condition and in the action as a destination for the "jump to page" rule, it should be disabled in rule action. With this we avoid mistakes and validation errors while executing the rule;
7. Keep sending the data on the backend side.
Product Design Prototype:
- is related to
-
LPS-68227 As a form builder, I would like to allow the form user to jump to another page depending on a checked answer, so that he/she does not have to answer to irrelevant questions.
-
- Closed
-