Save and Return UX

[dthomps1]

User feedback - when returning to a claim, users are returned to page 1, rather than the page they left. Details are saved, but users comment that they would rather return to the page they left.

[matias-eduardo]

You could add a navigation_stack similar to the one in the tax tribunals-datacapture repo.

This implementation is super simple and adds two key pieces of functionality: 1) saves the current step so that I can take the user directly to it, and 2) adds a working back button.

The only difference in my implementation is that I call the update function explicitly within the "show" step page rather than using a before_action callback.

Here's how it gets saved on the db:

navigation_stack: [
   "/profiles/16/steps/name",
   "/profiles/16/steps/email",
   "/profiles/16/steps/do_you_have_a_linkedin",
   "/profiles/16/steps/linkedin",
   "/profiles/16/steps/use_linkedin_as_resume",
   "/profiles/16/steps/are_you_currently_in_pr",
   "/profiles/16/steps/current_location"
]