October 2, 2019
Custom buttons – Gating – Slide revisit
Comments
(2)
October 2, 2019
Custom buttons – Gating – Slide revisit
(2)

For our captivate project, we have to use custom buttons because of some of the LMS requirements. (Yes-no prompt on exit button for example).

Each slide is supposed to be gated so that the next button isn’t available until the end of the slide AND it has to be available when the slide is revisited without having to review the entire slide again.

Right now I have the next button hidden and an advanced action executed on the load of the slide that delays the SHOW of the next button until the end of the slide (based on literal seconds). ¬†This works fine and even works fine when you go back and forth within the same session/viewing. However, when you close the module mid-way through- and try to go back to previous slides–it now is waiting until the delayed number of seconds-learner has to sit through the whole slide again.

How can I modify my action or what can I do to tell Captivate to show the next button on slide revisit–regardless of whether it is the same session or a new session?

This is pretty urgent for me so any help you can provide would be greatly appreciated. Oh and I am on the latest version of Captivate.

Julie

2 Comments
2019-10-13 11:08:11
2019-10-13 11:08:11

I use mostly micro-navigation to force viewing the first time, and jump to the Next timeline on following visits. Delay command is not always optimal, because its timer continues even when the learner pauses the slide.

However the problem is the same for another session. You need to track the visits for each slide with a Boolean user variable, and use either JS or the CpExtra widget by InfoSemantics to retrieve the value of that variable using local storage. This works when the learner will be on the same system. Ideally you could retrieve the value from the data sent to the LMS, but I learned that is rarely possible.

Like
2019-10-10 08:26:05
2019-10-10 08:26:05

It’s hard to advise how exactly you should modify your action without having seen it.

You’d basically need to track with variables for every slide if that slide was attempted (or even better, completed), and then conditionally show the Next button right away or at the end of the slide. Since you say that you have a solution that does that within a session, even when jumping around, I take it that you already do that with your current action. So the problem is to persist the values of those variables across sessions. Apparently some LMSs simply don’t support this, while others do. At any rate, you’d need to make sure that LMS Bookmarking is switched on (‘Never Send Resume Data’ unchecked), and that your tracking variables don’t have default values (because they would take precedence on course re-launch over what the LMS stored).

Like
Add Comment