Menu created using Advanced Actions not holding state in LMS

[PurplrPushPin]

I have a menu that was created using Advanced Actions where the user can complete the topics within the course in any order. When a topic is selected the button is hidden and a “grayed-out” version of the button is displayed indicating that the topic has been selected. When all topics have been selected and the user returns to the menu slide for the last time a button displays so that they can go to the exit sequence. A counter is used to control when the button displays.  If a learner exits the course before it is completed, everything is reset and they have to start over from the beginning. I’m looking for help on setting that could be used to prevent this.  The LMS vendor suggested editing the SCORM manifest but had no suggestions on how to do so.  We are using SCORM 2004 and Captivate 7.  We plan to upgrade to Captivate 9 soon.

[RodWard]

Your Menu slide would only be able to retain the counter variable values if you persist these values outside the module itself.  The LMS will (in most cases) be unlikely to store the values of the counter variables.  It's got nothing to do with the imsmanifest.xml file.  It's just that default LMS behaviour is to look at what the SCORM standard stipulates it should be doing.  And there's nothing in the SCORM standard that says it has to accommodate all possible implementations of menus created inside a SCO.

Some LMSs do apparently record Captivate user variables, but most do not.

Captivate 9 has not changed this behaviour.

If you are publishing your courses to HTML5 there is a new widget for Captivate that will soon be released that DOES allow you to persist user variables to Local Storage and this might potentially provide a solution for you when it arrives.