4 Replies
Harri C

Hi Kat,

I'm assuming you're tracking via slides viewed, if that's correct you'll run into issues with branching.

What you could do is disguise a quiz and results slide and report on that.

For example on one of the slides towards the end of the course that everyone will view create a 'convert to freeform' pick one and place a correct and incorrect button off screen. Then use triggers to change the state of the correct button to 'selected' when the learner clicks next (then jump to slide). Then add a results slide and change the aesthetics completely so it just looks like an ordinary slide and then report on quiz results.

Hopefully that makes sense


Ashley Terwilliger

HI Kat,

The method Harri is describing to submit completion based on a particular slide being visited is described here with some screenshots and such.

Also, if you're tracking by slides viewed you could set it to track by 3 less slides - that way if the branched around it, they'd still be considered complete but there is also potential that they could be complete without seeing 3 slides you consider necessary.

Kat Spaulding

Thanks Harri & Ashley! After spending the day trouble-shooting, we decreased the viewable slides by 3 and republished.

However, we're still having some issues after bookmarking - testers who got out of the course, resume where they left off and complete the course are still not being marked complete. We may have to add the disguise quiz/results page. Unless you have any other ideas? This is the first time we've had completion issues.

Ashley Terwilliger

Hi Kat,

I've heard of it when tracking by a results slide and the other conditions mentioned here. Since you're tracking by slides viewed, I'd want to know how it behaves at SCORM Cloud, which is an industry standard for testing SCORM content. Can you test it there and try to follow the same steps these other users took to receive an incomplete status and let us know how it behaves? if it behaves as expected there you'll want to share those results with your LMS team.