Repeat Quiz button will not always work and we want it to even if they pass

[argopellter]

We have a Quiz we have set up in all of our captivate files. It is general knowledge so they do not have to pass but we use the retake quiz button so they can retake it if they want.

The percent pass was at 80% because we did not change it since we did not care if they passed. So the retake quiz works if you are under 80% but we would like it to work in all situations, but because it is part of the quiz functions we have little control of the button.

Is there a way we could do it?

I have tried removing the buttons and just putting a regular button over it, but it always jumps to the last question the first time you hit it, even though I send it to the first question. After that the button works. Also it leaves the old answers in it, although you can change those.

Just wondering if anyone could help, or give us a work around.

Thanks,

Paul

[RodWard]

The Captivate developers have provided no way to change the default quizzing functionality here.  If the learner achieves a passing score then the Retake Quiz button does not appear on the Quiz Results slide.

However, if perhaps you are using Captivate 9 and your quiz questions are not really intended to be a true assessment anyway, why not replace the quiz questions with Knowledge Check questions instead?  Have you tried that?

[argopellter]

Thanks Rod,

I said general Knowledge but I meant Knowledge Check, that is what we have, but it still does not let us use the Retake Quiz button if you pass the quiz.

[RodWard]

Paul,

I don't think you and I may be speaking about the same "knowledge check" questions here.

Captivate 9 introduced a new type of quiz question called Knowledge Check that have no score and do not report to the Quiz Results slide.  So the Retake Quiz button does not apply to them the way it does to normal quiz questions.  When you leave these Knowledge Check slides they reset again. 

Are you sure these new KC question slides are the types of quiz questions you were referring to in your post?

[Pat Tastic]

We had a similar issue.  We wanted to allow users to retake for a higher score, if they desired. 

We accomplished this by creating a submit all, formatted quiz with a custom "progress" slide that is presented to the user at the end of the sequence of questions but before the final results slide.  I can breakdown further if you'd like, but in the interest of time, here's a simple take on what it does.  We used a combination of the advanced actions and on-slide system variables to accomplish this.

• When user gets to progress slide, captivate code determines whether all the questions have been answered.  If not, it presents the user with an "incomplete" alert via text box and a button that brings them back to the first question. 

• If they have completed all questions, then it uses a bit of code to calculate the score. 

• If the user has not achieved the 80% minimum, then it displays an alert via text box that displays their score (and says they must achieve a higher score in order to complete the course) as well as a button that takes them back to the first slide. 

• If the user has achieved a score equal to or greater than the minimum of 80%, the user is then presented with a text box congratulating and letting them know that they can now either retake for a higher score (by pressing the button to take them to the first slide) or they can commit their score to the lms (by selecting other button set to "advance to next slide"). 

• If they do commit their score, they then have to "confirm" this choice via the captivate pop up "submit all" box which is a bit redundant, but isn't too bad, and seemed to be the only way we could accomplish this.

I think that about sums it up. 

ps. Though the exact reason escapes me at the moment, for our purposes we did also find it necessary to adjust a bit of javascript from the scormdriver.js file in the published package.  It defaults to false, so we changed it to "SCORE_CAN_ONLY_IMPROVE=true"

Also, with the exception of the final results slide, we used all custom made buttons and would simply drag the default buttons off to the side.

not a perfect scenario, but hope this helps.