Storyline Known LMS/Tracking issues

[SL-09] Drag-and-Drop "Undefined offset: 1"

Error in FiLMS for quiz question

Steps to Reproduce:

• Take drag-and-drop

Possible resolution

TBD

[SL-08] Resume-No Flips Completed Status to Incomplete

This is a feature of Storyline. Storyline resets Lesson_status=Incomplete when a user relaunches a course and chooses "no"

Versions affected: All

Steps to Reproduce:

• Enrollment status=Completed/Passed

• User relaunches course

• User selects No when prompted to Resume where they left off

• User closes course without recompleting

• FiLMS/eco shows status=Incomplete

Possible resolution

If the client does not want users to be able to Incomplete a previously completed course:

• Publish Storyline course with "Always resume" instead of "Prompt to resume" or "Never Resume"

• Configure FiLMS to Prevent this behaviour: Prevent FiLMS from setting Course Completion to Incomplete upon relaunch

[SL-07] FiLMS Mastery Score Override

On Fri, Jun 22, 2018 at 11:37 AM, Grant Angus <gangus@icomproductions.ca> wrote:

Hey folks,

So we've looked into how Storyline deals with mastery scores and it must be something that just hasn't come up alot recently as most courses track by view completion rather than quiz completion.

In storyline you define the passing score in the results slide which in SCORM Cloud or other LMS's is where the LMS will get your mastery score and it works just fine, no configuration needed. On QA3 however apparently our course configuration setting (Use to be how we changed language) overrides storylines mastery score setting. This is something that hasn't really been updated since our flash courses and might be something we want to look at updating on QA3 in the age of storyline.

So the fix will be whenever we have a quiz completion we'll need to make sure we change the course configuration setting and/or get a new template made for each different mastery score (a 75% one does not exist, we've been testing with a 70% one).

Thanks,

Grant

Steps to Reproduce:

• Course configuration mastery_score=80%

• Complete course with 75%

• Course submits score of 75% & Status=Passed

• FiLMS records score of 75% but "corrects" status=Failed because it's less that mastery_score

Possible resolutions:

• Edit Course configuration to ensure Mastery score matches passing score in Storyline

[SL-06] Complete course flips incomplete

Colin

Colin Bittner added a private note 15 days ago (Thu, 10 May at 10:54 AM)

Notified to : support@icomproductions.ca , cc : kjones@icomproductions.ca

Storyline calls it the "course complete trigger" - it's a feature exclusive to SL360 right now, but if it is added, the files can still be opened in SL3.

Prior to them adding this feature, courses could only be marked complete to the LMS in two ways: either a threshold of slides viewed (problematic because we have many courses with branching or optional slides, meaning you might not meet our threshold) or based on the scored results of interactive questions (aka a quiz, problematic because there are plenty of courses without a quiz). In the past, to get courses to complete exactly where we wanted them, we would fake a quiz question, had have the button you'd click to complete the course submit the correct answer for the question, and then the total results (always 100%) to the LMS. This is janky as hell though and not really a very intuitive solution, since it requires a lot of out of the box thinking, and a bunch of setup.

They've now added what they call the "course complete trigger". In Storyline, triggers can be used to create actions or changes on screen (ie. "Jump to slide X when the button is clicked", "Show Continue button when x, y, z are true", etc.). These triggers are pre-built, so we cannot create custom triggers. Thankfully, this trigger can be placed ANYWHERE in the course, and then mark complete based on that trigger. So we can have "Complete course when the timeline starts" on the last slide.

You guys can certain add it, it's about a 2 minute change + publishing. I gave Ken a rundown of SL in the past, would something similar be helpful for you so you can make minor adjustments yourself?

[SL-05] Inconsistent behaviour on course relaunch

Always make sure your enrollment in the course is reset before testing a recent update to the course, otherwise old data will be stored via SCORM and cause inconsistent bugs.

Solution

Reset enrollment

[SL-04] Course Not Completing

If you're struggling to get the appropriate completion on your courses make a Results slide, ensure that 'submit results' is added as a trigger. If it's the last slide, its recommend to add a 'pause timeline' trigger, then create a button to exit the course, this helps ensure content is sent to the LMS. This can also be used to set completion if you're looking to track a specific part of the course.

[SL-03] LMS Completed Status Reverts to Incomplete

A Storyline course can ignore the Force Complete of an LMS under some circumstances setting it's status to Incomplete. Storyline courses will also try to change their status to Incomplete if a user chooses to click No when asked to resume. FiLMS, as an example, allows courses to incomplete themselves by default but other LMSs may not.

To direct FiLMS to Prevent this behaviour see this article: Prevent FiLMS from setting Course Completion to Incomplete upon relaunch

[SL-02] Slides not marking complete due to menu

Storyline generates headers based on scenes and slides, which in some cases will have the same title in our courses. If you accidentally delete a slide title, and leave the scene title, it will never mark that slide or scene as complete. Scenes only mark complete if all the slides within that scene mark complete.

Solution

So always delete the scene titles rather than the slide titles otherwise you could cause this marking completion glitch.

[SL-01] SCORM 1.2 bookmarking issues (suspend_data)

Storyline courses can develop issues with bookmarking because of a SCORM 1.2 element named suspend_data. Storyline adds bookmarking data to suspend_data as users take the course. This data may become too large for 3rd party LMSs to store because the SCORM 1.2 specification sets a maximum character limit of 4096 characters. When the character limit surpassed the course resumes on the last slide nearest the value.

More detail:

• https://community.articulate.com/discussions/articulate-storyline/scorm-1-2-suspend-data-seems-wonky-to-my-pea-brain

• https://articulate.com/support/article/exceeding-scorm-suspend-data-limits

FiLMS should NOT be affected because it uses the MySQL data-type of TEXT to store SCORM element data (scorm_elements.value) which has a limit of 65,535 bytes (21,845 to 65,535 characters dependent upon encoding)

Solution

The following changes might be able to resolve the issue, but there's no guarantee:

• Publish to SCORM 2004 3rd or 4th Edition or Tin Can/Experience if you can or LMS supports

• Reduce the number of slides in a course

• Reduce the # of layers in a course

• Consider using lightbox slides for layers that repeat over many slides or come from masters

• Set as many slides as you can to "reset to initial state" if you can

• Reduce the number of questions in a quiz or cut any freeform interactions that you can

• Use freeform questions instead of text-based questions as less data may be sent

• Reduce the use of long-form variable strings

This issue has no impact on the reporting/tracking of progress or completions in the course, only on the resuming of the course.

More troubleshooting

• http://blogs.articulate.com/word-of-mouth/9-ways-to-troubleshoot-articulate-lms-issues/?_ga=1.77343703.318332625.1458322506