Adapt Learning Community: Bookmarking/trickle issue

Hi there,

The courses we create in Adapt all have a video as the first component and this is set to mark as complete when 'ended' - this is followed by an automatic trickle which scrolls to the next component.

This forces users to complete the video before moving on, but does seem to make bookmarking tricky, as the user always has to complete the video before moving on, even on revisit. (We have the 'Locked on Revisit?' Trickle option set to false on all blocks).

I was wondering if there is a clever method for removing trickle on revisit when the course is used in an LMS?

Hopefully this all makes sense!

Thanks for your help in advance,

Ali

Hi Ali

For the moment you need to set the _completionAttribute to "_isComplete" in the configuration for trickle in config.json

(Sorry you didn't say if you are using the authoring tool or the framework, the above instructions are for the framework)

This is partly my fault, I've just remembered that we agreed back in Nov 2016 to make this the default setting but I never actually got around to making that change!

Show parent | Reply

Hi Matt,

Thank you for the suggestion.

That has helped to open up the course on revisit, which is great! However, the progress bar now doesn't fill as expected. If you complete a couple of components, and then leave and come back in, the course is open to that point which is great but then if you complete the rest of the course, the progress bar doesn't fill fully despite the menu showing each section is complete. This still feeds back to our LMS as a Completed Attempt so it appears to be a purely visual issue?

To fill the progress bar fully, you seem to have to interact with an earlier, completed component. I don't think a user would think to try this if they noticed the bar was not full, so I'm not too sure what to do to resolve this?

Any thoughts would be great!

Cheers,

Ali

Show parent | Reply

Hi Alison

No problem at all.

The issue you describe with the PLP is likely to be a very similar/related issue. Either that or you have two blocks with the same _trackingId.