"Save/Quit" & "Resume" Behavior Details?

Hi,
Several questions! Cornerstone is our LMS. Building in Storyline 3.
With player's "Resume" settings at default "Prompt to Resume," how exactly does that express itself in use and what exactly is preserved?

-Variable values?

-Selections & button states?

-Can the user quit by any means such as just closing the browser window/LMS session time-out, etc., or must there be a specific way/point at which they leave the course?

-Lastly, is there any way we can test the Resume performance locally, before deploying to LMS, to be sure we're delivering the right behavior for our users?

2 Replies
Judy Nollet

My main client uses Cornerstone, with courses always set to "Prompt to Resume."

  • A user can exit the course before finishing. This can be done by closing the browser window or by clicking the EXIT button (if one if provided).
  • When a user re-launches the course, they see a dialog box asking if they want to resume where they left off.
    • If they click "No," the course will restart from the beginining.
    • If they click "Yes," the course will restart from the slide they were on when they left the course.
  • The resume function remembers where the user was in the course, as well as all the saved states and variable values. In other words, when the user continues from where they left off, the course should behave as if they never left it.
  • Browsers aren't set up to store LMS info, so they don't ask about resuming; they just start from the beginning. With my client, we always load a course into their Cornerstone staging environment for testing it.
J H

THANKS Judy! This is brilliant. We are on Cornerstone.

"resume function remembers where the user was in the course, as well as all the saved states and variable values"  --  As in, their score will be retained and they can resume at will. Correct?

We also have the LMS staging testground so will make sure to double check all that, but sounds like this will do exactly what we need.  Brilliant. Thanks again. : )