Restarting project from beginning after failing quiz

Hmm, I have a similar issue. If anyone is able to work this out I'd be greatly appreciative.

The FIRST thing to do when trying to debug any SCORM related issues is to upload your content to SCORM Cloud and see if if behaves the same way there.  If SCORM Cloud handles it without issue, then your problem is likely to be that your own LMS is not as SCORM-compliant as it would like you to believe.  Having evidence in your pocket that SCORM Cloud doesn't have the same issue goes a long way towards forcing your LMS to come clean and provide you with more technical support.

If SCORM Cloud also shows the same issue, THEN you start looking deeper into settings.

I would also like to point out in the example above that perhaps using SCORM 2004 would be a better option than using SCORM 1.2 as the later SCORM standard provided a way to track completion status separately to pass/fail status, whereas SCORM 1.2 only had one variable to do both.  Using the project end options to call another SCO is not going to solve anything as SCORM requires that the LMS initiate the launch of each SCO in order to track them properly. 

Using JavaScript to make SCORM calls is possible, but you need to really know quite a bit about SCORM and JavaScript to pull this off, and it can mean you end up with more of a maintenance overhead in the end.  In general, I believe it's better just to run with the vanilla options provided in Captivate itself.

There's plenty of information on the web about the JS API for SCORM, so a good JS person shouldn't have too much trouble working out how to make the calls.  But be advised that there is quite a lot of variation between LMSs as to support for SCORM.  So if you DO go the route of rolling your own JS calls you may end up with a solution that really only works predictably on your particular LMS.

Take a look at this page from the Rustici site about the differences between the standards:

http://scorm.com/scorm-explained/business-of-scorm/scorm-versions/

With SCORM 2004 you have to remember that the Completion variable is only really looking at whether the user completed a given percentage of the content, not whether or not the passed or failed.  In Captivate, as soon as you select either SCORM 1.2 or 2004 you can very clearly see how the options change. 

In Cp's SCORM 1.2 dialog the upper Status Representation area is asking you to select which of only two options you want to use for describing the final status of the module.  The Success/Completion Criteria area is allowing you to determine HOW that upper status will be decided, not how it is represented.

In the SCORM 2004 dialog, since there are now TWO separate status variables (one for completion and another for pass/fail) each section gives you options to decide HOW the status is determined.

It may take a bit of trial and error to find the right combination of settings, but SCORM 2004 is definitely more versatile than 1.2, however, the majority of the LMS users around the world are still using 1.2 because it is less complex and more widely supported by LMS vendors.

One suggestion if I may.  When you said that you have a big Advanced Action that jumps them back to slide 1 and does a lot of stuff, warning bells went off in my head.  I suggest you NEVER do any advanced actions on the very first slide of a project.  The On Enter slide event of that first slide can be unreliable and the actions attached to that event may not fire properly when the project is still loading up the first time.  So, I recommend you make that first slide blank and maybe only a second or two in duration.  Jump your user back to the SECOND slide of the project and make that one the slide where your big AA does its stuff.  Much more reliable.

I didn't see that you have a complicated advanced action that is executed at the On Enter event of the first slide. But when reading your descriptions, I have a slight feeling that you are making the advanced actions more complicated then necessary.  I cannot be sure without seeing the real scripts of course, it is just a little bit of advanced actions intuition.

Lilybiri

I am trying to do something similar.  Just a question -- when the Restart Course button set the variables back to zero -- are these user variables or system variables or both?

Still learning about Captivate and trying to figure out how the quiz variables get reset if you send a learner back to the beginning of a course once they have failed.  Thanks.

Quizzing system variables are reset when the user uses the Retake button on the score slide, as long as there are attempts on Quiz level available. It is not sending them to a slide that will reset the variables.

Question Question Slides in Captivate - Captivate blog

Question Question Slides - Part 2 - Captivate blog

And I used this knowledge in Reset Knowledge Slide - Captivate blog

Thank-you for your reply. That's what I thought.  I have read your blog posts and I think I understand what you are saying.  But the "reset" article doesn't really get me to a solution for the situation I am trying to address.

Here's the scenario -- I want to be able to provide a learner who fails a quiz the option of either retaking the quiz without further review (which is what the retake button does) OR if the learner fails on the second attempt of the quiz, I want to give them the option to go back to the first content slide and then be able to retake the quiz.  If you can't reset the quiz variables using advanced actions, I don't know how to make the option of reviewing the content and then retaking the quiz happen using Captivate 8.  I suspect that it may not be possible within the Captivate file.

Any information you have would be appreciated.

All quizzing system variables are read only. You cannot change them.