January 6, 2020
Visited state issue in bookmarking using js var
Comments
(5)
January 6, 2020
Visited state issue in bookmarking using js var
Newbie 2 posts
Followers: 0 people
(5)

Hi guys,

I have developed a course in captivate 2019 having around 60 slides and on each slide enter the tick mark will show on the respective topic in TOC(Customized design) and also the active state showing for current topic alone.. I did this by using captivate js to reduce work a bit.. I mean to reduce a number of captivate actions, trigger.. And now all visited and active state for all TOC is working perfectly fine in local..

The problem here is my course is scorm enabled.. So i went onto check the course in scorm cloud for course completion status and bookmarking.. Here also everthing works fine in the very first attempt(TOC visited states and active state) and to the mid way of course i exited the course and relaunched the course to check bookmarking.. Then, the bookmark is works fine(starts from where i left off) but all the visited and active states are gone from TOC and also the states are not appearing for the next corresponding screens..

I think this is happening because of the usage of js variable instead of captivate variable to activate the state for TOC..

It would be bit frustrating, if i have to use captivate var to do the recommended job..

Could you guys have any idea about how to tackle this situation.. Any idea would be much appreciated..

Thanks much in advance..

5 Comments
2020-01-07 13:15:47
2020-01-07 13:15:47

Another benefit of naming the variables in Captivate as well is that you can dynamically display them using the  $$variable$$  convention for troubleshooting purposes.

It is a great way to verify if your variable based triggers are behaving the way you expect.

Like
(2)
2020-01-07 13:06:35
2020-01-07 13:06:35

I would add two things – and perhaps I completely missed the point but maybe they will help.

  1. Have you checked the box to ‘Retain State on Slide Revisit’?
  2. I have gotten into the habit of whenever I use JavaScript to work with variables – that I always name it as a global variable in Captivate. I simply have overall better outcomes doing that.
Like
(2)
(2)
>
Greg Stager
's comment
2020-01-07 13:25:20
2020-01-07 13:25:20
>
Greg Stager
's comment

Greg, I had understood that it was about the completed checkmark in the TOC, may be wrong of course.

Captivate has only one type of variables, global variables are typical for JS. Can you explain what you mean?

Like
(1)
>
Lieve Weymeis
's comment
2020-01-07 14:14:22
2020-01-07 14:14:22
>
Lieve Weymeis
's comment

I just used the word global because when I name the variable in Captivate it becomes easily accessible throughout the entire project. In some cases I have had problems that were fixed by simply declaring the variable through the UI in Captivate.

I may not need to but I’ve made it a habit and now I have much fewer issues of that particular nature.

Like
(1)
2020-01-07 09:10:34
2020-01-07 09:10:34

This doesn’t look like a sample project or asset, but as a question (labeled discussion).  Moderator????

Where is the project? I often use JS to manipulate variables from Captivate. Did you exchange the values?

Like
Add Comment