Codify, improve and write better documentation for Auto Save url

[mitch-mitchel]

Note: they would like the option to go back to the same resume behaviour of going to the front page, as they custom logic there to offer the end user

CLEO is looking to implement the auto save feature, with ideally a save on each continue, page change or fall back to timer
Also re-visit the manual save and exit flow to be simpler for the end users
Make it optional to start at page 1 (CLEO uses custom logic to check)

from their notes:

1. Emphasizing Save and Exit

For CALI: When user hits button, instead of going to a question/set of questions in pathway, could A2J Author display an overlaid pop-up which explains saving and exiting, and allows user to exit pathway
from here? I'm imagining this would look like how pop-ups look but could have the pathway fade-out in the background too, to further emphasize the Save and Exit pop-up.

2. Expedited Save and Exit

For CALI: Can we enable instant, automatic saving when hitting
SAVE AND EXIT button (create partially completed answer set), without having to click through to the second Exit

3. New save and continue

For CALI: Can we enable the creation of an answer file without ending the Guided Interview?

For Run Straight: If enabled by A2J Author, can we save a partially complete answer set without ending the session, saving the data collected in the A2J Guided Interview to RS HUB while allowing user to continue, overwriting this file when the user next
saves?

For Run Straight/CALI: If yes to the above, would it be possible to facilitate continuous automatic saving as the user proceeds through the pathway, for instance, whenever user proceeds to next question
and/or on a timer (e.g. every 60 seconds)?

[mitch-mitchel]

User Stories:

• as a user, I would expect my interview progress to be auto-saved as I go, at least after a page is completed (aka hit continue)
• as a user, I would expect if I have page partially filled out, and there is x minutes of no activity (typing, scrolling, etc) I would expect a save to fire in case I walked away and come back later to find it logged out, or in use by someone else
• as a user, I would expect the system (A2J.org, LHI, CLEO) to know who I am, and restore or offer to restore my progress if I return to an incomplete Guided Interview.
• as a user, I would expect to be able to go back 2-3 save versions, especially if I want to to undo to a previous state (stretch goal maybe)
• as a user, I would expect a failed save to have at least 1-2 previous saves to go back to should something happen to the current auto-save, minimizing my loss.
• as a user, i would expect the auto save to be aware of my bread crumb trail of pages visited and any navigation triggered by buttons or logic to refire as expected, and/or highlight the navigation button clicked so that I can 'work my way' back through the interview and review my steps/answers (stretch goal)
• as a user, I would expect to be able to download my answers in some human readable, but system restorable format that I could later manually upload to continue a partial interview, or reprint a document, or re-send answers to an intake server.

[mitch-mitchel]

Dev Stories:

• as a dev, I would expect the answers format to be easy to consume and read (aka JSON), contain answer values for answered questions, and also a nav history that can be restored for the user
• as a dev, I would expect to be able to save those answers to local cache, file system, or API endpoint depending on the complexity of the hosting environment
• as a dev, I would expect there to be a recovery process for a failed save, as well as some kind of notification (to the user as well)
• as a dev, I would expect a control for enabling or disabling auto-save either on a server level basis, individual guide basis, or both
• as a dev, I would expect the auto-save would offer some form of auto-cleanup, rotating stack of backups to prevent a server or file system from being overwhelmed with backup files.
• as a dev, I would expect to be able to save/export a Guided Interview with it's current answer file to be loaded on another system for testing (stretch goal)

[MaxS-CLEO]

Hi Mike,

Here are a few additional user stories, based on feedback we've gotten from our users:

• as a user, I would expect there to be a save button as well as the save and exit button.
• as a user, I would expect for each Step that was completed to be automatically saved for registered users (i.e. some sort of notification in Viewer upon completing a Step and proceeding to the next one. A message saying "Step 1 completed" after proceeding to Step 2"