Follow

Managing recurring assignments

Avatar

We’ve got some big news! We’ve added some new functionality to the way we handle Dispatches, which we are calling Dispatch instancing.

Why would you use Dispatch instancing, you ask? Let’s say you have learners that need to take the same course every six months,  a CPR training course, for instance. Without Dispatch instancing, you would have to create a new Dispatch every six months to deliver your recurring training. Rather than do that, we’ve made it easy for learners to take multiple “instances” of the same Dispatch package.

How does it work?

When the learner launches the Dispatch course from the host LMS, SCORM Cloud will look to see if this is an existing registration from the LMS, or a new one. If it's a new registration, SCORM Cloud will create a new instance. If it has been launched before, SCORM Cloud will relaunch the existing registration. So in our example from earlier, if your learners need to take CPR training every six months, the host LMS creates a new assignment every six months. Each registration will now have its own associated SCORM Cloud registration.

Each instance is tracked as a separate registration. So it’s important to note that each instance delivered will be charged as a separate registration. This functionality applies to all Dispatches from June 22nd forward - including Dispatches created and delivered prior to this change.

It is important to note that the host LMS must support SCORM 1.2 suspend data functionality to use Dispatch instancing. If they don’t, it will revert back to only allowing for one registration per learner for a Dispatch package.

If you have any questions, please let us know. We’re always here to help.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk