-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Conditional Input History - Form Builder #3859
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🧪 Review environmenthttps://qe6jbbouycwkmgjskewnkirulq0xshhw.lambda-url.ca-central-1.on.aws/ |
thiessenp-cds
changed the title
Conditional Input History (WIP)
feat: Conditional Logic: Conditional Input History (WIP)
Jun 19, 2024
thiessenp-cds
changed the title
feat: Conditional Logic: Conditional Input History (WIP)
feat: Conditional Logic: Conditional Input History
Jun 25, 2024
thiessenp-cds
changed the title
feat: Conditional Logic: Conditional Input History
feat: Conditional Logic: Conditional Input History - Form Builder
Jul 17, 2024
thiessenp-cds
changed the title
feat: Conditional Logic: Conditional Input History - Form Builder
feat: Conditional Input History - Form Builder
Jul 17, 2024
timarney
reviewed
Jul 18, 2024
timarney
reviewed
Jul 18, 2024
timarney
reviewed
Jul 18, 2024
timarney
reviewed
Jul 18, 2024
timarney
reviewed
Jul 18, 2024
timarney
reviewed
Jul 18, 2024
timarney
reviewed
Jul 18, 2024
timarney
reviewed
Jul 18, 2024
Co-authored-by: Tim Arney <[email protected]>
Co-authored-by: Tim Arney <[email protected]>
timarney
reviewed
Jul 18, 2024
timarney
reviewed
Jul 18, 2024
timarney
reviewed
Jul 18, 2024
timarney
approved these changes
Jul 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary | Résumé
Adds the conditional input history feature to the form-builder and Review page only. A followup PR will add this feature to Forms-forms submissions.
More Info:
Using the group history logic to allow a user to navigate the conditional logic in a form, update the user answers (form input) to only include answers that follow the users navigation.
For example, a user may go down conditional logic option A but then later go back and choose conditional logic option B, then follow the option B branch. So the questions answered on option A's branch should not be included in the form submission, only the answers from the option B branch.
Testing
Note: show/hide value filtering is applied on the form-builder only. So submitting a form will still have the previous functionality of including both visible and hidden values from any show/hide elements.
Ideally test creating a form with conditional logic in both the Form-Builder Preview. Try going down a few conditional logic branches and check if the answers you inputted match the "conditional input history" you navigated within the form.
Here is an example manual test that focusses on making sure the correct "history" of answers is on the Review page. The user chose the A conditional "branch", so only those answers should be in the form submission. Not the branching answers the user also answered from going down the B conditional and C conditional branches (though those answers remain in the form inputs for user convenience).
Screen.Recording.2024-06-27.at.11.21.51.AM.mov