What happens when a user hits "Back" on contact-representative?
The team discussed and decided...
If the user hits "Back" in the same session:
The selected representative is null-ed out
The user can see the query they just entered
We'll cache the user's rep query on the frontend to support this
The user will need to select a rep (same or a new one) to move back to contact-representative
If the user tries to "Continue" we will throw the validation error
If an authenticated user leaves the form experience and revisits the representative-selection page later via the "Back" button, they will see the default flow:
The selected representative is nullified
The user will need to reenter their query (we will be unable to preserve because this is a new session)
The user will need to select a rep (same or a new one) to move back to contact-representative
If the user tries to "Continue" we will throw the validation error
Tasks
[ ] Implement frontend logic to preserve a user's representative query in the same session
[ ] Implement frontend logic to nullify the rep selection, if the user hits "back" to revisit the representative-selection screen
Acceptance Criteria
[ ] When user hits "back" to the rep-selection page, they are able to see the representative query they just entered and can re-select a representative from the search results.
Background
What happens when a user hits "Back" on
contact-representative
?The team discussed and decided...
If the user hits "Back" in the same session:
contact-representative
If an authenticated user leaves the form experience and revisits the
representative-selection
page later via the "Back" button, they will see the default flow:contact-representative
Tasks
representative-selection
screenAcceptance Criteria