State and variable changes don't save when resumed
Oct 30, 2013
We have found that courses that include states and variable changes don't save when a course is exited and resumed. The attached Story file includes a very basic example of a course that includes a state change in buttons on the second page of the course. The first page includes a variable that is modified based on state changes on the second page. If the second page is completed so the user returns to the first page, and then the course is exited, the state changes stick. However, if the user only completes part of the state changes on the second page before the course is exited, if the course is resumed, the state changes are not remembered, even if the page is set to resume saved changes. The same situation occurs if variables are used instead of state changes.
This is very problematic in pages that include many tasks resulting in state or variable changes that must be completed before the user completes an overall task. In the attached example, the first page links users to a second page in which the user must view two layers. Once both layers are viewed, the associated true/false variables are changed, which result in the main button on the first change moving to a state of completed. If only one layer is viewed on the second page and the course is exited, upon resume, the work completed during the first attempt are not saved. This action was tested on our LMS.
Is there any way to get the variable and state changes to be written to the LMS so they can be resumed on subsequent course sessions?