Resume behaviour of Articulate, Captivate and other xAPI Content

Estimated reading time: 1 min

Most of the authoring tools including Articulate, Captivate, iSpring and others support resuming the content from where you left.

When using Experience API tracking and GrassBlade, there are many ways this behaviour can be customised and controlled using the “registration” property in xAPI Content page.

Method 1
Always Resume: Use a fixed registration value:

Purpose: You want the content to always resume from where you left. Even if you have completed the content.

Solution: You can use a fixed registration value for attempt. The value must be in UUID format, for example: 36fc1ee0-2849-4bb9-b697-71cd4cad1b6e

Find this setting here:
xAPI Content edit page > xAPI Content Details > Override Global Settings > Registration

Note:
It will reset the progress of all the in-progress users and they will start from beginning. Now the resume will not reset even after completion.

Method 2
Resume till incomplete

Purpose: You want to be able to resume from where you left. However, after the content is completed, you want the resume to be reset, so you start from the beginning next time

Solution: You can leave the registration value as blank, or set the registration value to: auto

Method 3
Resume for Guest Users

Guest Users, i.e. the users who have not logged in the WordPress site cannot resume using “Resume till incomplete” method mentioned above.

Purpose: You want resume feature for guest users to work.

Solution: You can use the method 1 above: “1. Always Resume: Use a fixed registration value”.

Downsides:

All users along with logged in users will be on the method 1 now.

If “Allow Guests” is selected:

  1. An email id based on IP is used for user identification. So, resume will work only if IP doesn’t change.
  2. If another user with same IP visits the content, he will be assumed to be same user, and content will resume.

If “Allow Guests (ask Name/Email)” is selected:

  1. The provided email is used. So, if the user enters another email id, he will resume where user with that email id had left.

Tips:

  • If you have many content, you can change settings of all contents using Bulk Settings feature.

Read More: Completion Tracking Not Working

Was this article helpful?
Dislike 0 11 of 11 found this article helpful.

2 thoughts on “Resume behaviour of Articulate, Captivate and other xAPI Content”

  1. I am not sure what this means. Right now, my lesson videos are not resuming at the place they were at when a person hits Mark Complete button. They reset the video which is bad. The Registration thing is set to Auto. So are you saying that if I merely put a random UUID number in that field to replace the word auto. Suddenly, my videos will resume? Can you explain why that would be the case?

    1. Pankaj Agrawal

      Hi Mike,

      I can understand that it may not be immediately intuitive to understand the concept, unless you are coming from SCORM background. “Registration” is a SCORM property, (and subsequently adopted by xAPI). It denotes a specific enrollment instance (a specific content for a specific user). So, as long as all progress of the user taking the content is attributed with a specific registration value, it is assumed that he is taking it as part of that enrollment.

      If the registration value changes, it means this is a fresh enrollment. For example, if you need your employees to take HIPAA course every year, they might need to take the same course again and again.

      The default functionality resets the progress on completion by changing the registration value. So, that the course can be taken again a fresh.

      Forcing the registration value to a particular string will make sure, it doesn’t change even on completion.

      Pankaj

Leave a Reply

Your email address will not be published. Required fields are marked *