Articulate 3 created course delays in posting cache results to the LMS
Aug 24, 2020
Hi All
My client is using Articulate storyline 3 and has created course that only contains an assessment. There is a limit impossed on the amount of failures the learner can attempt before the course is locked. Once locked the learner needs to request a training manager to unlock and reset the course to continue. Here s when the issue presents itself - if the manager unclocks the course and closes the window too quickly the suspend data is not communicated to the LMS API in time and the course is 'stuck' on the screen used to unlock the course - if the manager waits a few seconds after unlocking the course before closing the window the course behaves correctly. Under developer tools we have observed that course caches values throughout the course and posts SCORMEXECUTE commands every now and then - we have also observed that upon closing the course after the last SCORMEXECUTE command has been posted, the course functions correctly. I would appreciate assistance in determining where the issue could be so that I can rectify. The client is using Chrome version 80 and above, the LMS is a bespoke development.
9 Replies
Hi Andrew, I'm not sure if this relates to your case, but the update of data to the LMS is triggered when a slide is navigated from. Therefore, if updates have been made on a slide, and the slide is not navigated from, any variable/state changes will not be saved. It might be best to include a trigger that performs a navigation away from the slide, to ensure the latest data is saved.
Hi Sam
Thank you for the reply. Will this explain why the few seconds wait will resolve the issue as the normal course of the Course communication to the LMS API still occurs but if there was a triggered event away form the course then this will occur natively in an instantaneous way?
Hmm, I'm not sure why the few seconds wait is required. This might point to another problem. Would you be able to share a stripped back version of the unlock process so I can take a look and see if I can spot anything withing the Storyline file that may cause the issue?
Hi Sam
I have requested the storyline 3 story file from the client, this is to determine if the triggered event is associated correctly - failing this, can I reach out to you once again with my findings?
Sure. Take a look at the trigger and ensure all are running as soon as
possible, and not happening at the end of a needlessly long timeline.
Hi Sam, checked the storyline story file and there is indeed no Trigger from the failed attempts slide (the slide that is displayed after a learner has failed the course 3 times). What is confusing to me is that when run through SCORM Cloud - it works. I will need to answer this question before I can persuade my client to alter their course to suit.
SCORM Cloud may be evaluating the fail status automatically based on a reported score that is checked against a mastery score? This happens when their is a mastery score defined in the manifest file. Maybe I'm telling you something you already know, but thought I should share just in case.
Thanks Sam, for the insights and the assistance. I am going to try and enter a trigger from the last slide to test the theory. I'll let you know, failing that I'll try strip-out any customer identifying data and make it available to you directly, if you don't mind.
Hi Sam, found this link https://articulate.com/support/article/exit-course-trigger-doesnt-work-sl2 and once I applied it and republished the course it worked. Now I don't know why it would work by changing from SCORM Recommended to Always Close, and also I'm not sure of what this will mean to SCORM Compliance.
This discussion is closed. You can start a new discussion or contact Articulate Support.