Whenever i Publish the course in storyline 3, i set the report and tracking as Passed/Failed. Recently (after the update, maybe i am not sure), even if i set the settings as Passed/Failed it automatically changes back to Passed/Incomplete after publishing the course.
I am using Rise, in Rise i use quiz created in Storyline with result slide. In Rise i use the continue divider to validate whether the user pass the quiz or not.
However, if the storyline file setting is Passed/Incomplete the continue button automatically enabled after viewing the quiz and not passing it and user can move to next section without passing the quiz.
Kindly request you to check the last two updates (11 days ago and 2 hours back) of storyline because previously this error never happened.
Thanks so much for sharing those steps with me, Matthew. I'm seeing the exact same problem you're seeing. I agree with you that this is rather problematic, especially since settings are carrying over into new files. I'm going to bring this to my team now.
As soon as I get an update, I'll share it here. Thanks again for bringing this to our attention!
Thanks for your reply. Yes, i have published the course after changing the settings, still it automatically revert back to its original settings that is Passed/Incomplete.
Hello group, I was about to send a client a simple LMS test file created with SL 360. I, too, noticed that the "Report status to LMS as:" setting always reverts back to the default "Pass/Incomplete" option. I was intending on using the option "Completed/Incomplete" since this doesn't involve any scoring, and thus there's nothing to "pass".
I'm hoping that changing this each time I publish still carries over my "Completed/Incomplete" choice, and that it's just reverting when I next want to publish. I can deal with that in the short term.
Hopefully the Articulate team gets this resolved before too long. This would certainly mess up a real project where one is making edits/changes and re-publishing/re-delivering to a client.
This is using the latest version: "April 2, 2018 (Build 3.14.15225.0)"
I also see that the identifier doesn't remain changes after I edit it and publish it. It regressed back to a previous identifier. This is also in the "Reporting and Tracking Options" dialog box.
The file this happened with happened was a "converted to SL360" file. I had used that as a starter file . Even though SL360 converts the file when you open it, etc., I wondered if there was some sort of "legacy" effect, where the file was retaining some LMS settings from its earlier SL2 version. I figured I should re-test this and start with a blank, new SL360 file. It turns out that the issue is still present in that case - I just wanted to eliminate that as a possible strange scenario where my issue only happened if opening a SL2 file and using it as a starting point.
However, it did show me something that may be close to the matter at heart: New files use the previous file's LMS publish settings. When file A has an updated setting for "Report status to LMS as:", it doesn't retain that choice when I go back to the Reporting and Tracking screen. But when I create a totally new file, file B, and go to the Reporting and Tracking screen, I see file A's settings. And then file B will not remember any new choices I make.
Are people finding that it keeps the settings that you change when you publish it? I'm trying to get something to actually report a failure to the LMS, but it won't register as anything other than "incomplete". So I'm wondering if this bug is actually NOT changing it even when I choose to do so? Is there any word on when this will be fixed?
One of the fixes addresses an issue in Storyline 360 where: when publishing an LMS course, changes made to the reporting options (identifier, reporting status, etc.) would not always save.
Nice work, Articulate team! I've updated and given it a test swing; the items that I and others had found are now acting as one would expect. The settings remain after publishing, and after closing & exiting a file. Excellent!
I have noticed that my Storyline 3 course which is has the publish settings for the results slide of passed/failed and HTML5/flash fallback is reporting incomplete/passed instead of failed on our LMS.
What LMS are you using? Have you looked at testing in SCORM Cloud to compare the output? I'd also suggest when you test there and in your LMS you look at enabling LMS debug mode, as that'll help you see the data being passed back and forth. If you need help deciphering or translating that, let our Support Team know!
Thanks Ashley. We are using ESR. Weirdly when I retested in debug mode with a cut down version of the course that I tested on SCORM cloud the result recorded as failed on both systems. Very strange. Would size of course have anything to do with it?
It sounds like the cut-down version of your file reported correctly as "Failed," but the original version of your file reported incorrectly as "Incomplete." Is that right?
Would you mind sharing your original file with us so we can try and pinpoint why that's happening? You can send it over right here.
Yes that appeared to be the case. However, I tested it again yesterday and it is now recording as failed on ESR. It is very odd. I will keep an eye on it and if it happens again I'll send a file over.
18 Replies
This post was removed by the author
Yeah i have 360. I am using Rise too
This post was removed by the author
Hi GSC Academy,
It sounds like you're using Storyline 360 and not Storyline 3, is that correct?
You can use a course completion trigger in Storyline to send a signal to the Rise Continue button that the Storyline block above is completed.
I recently recorded a Peek about that very topic for another community member--you can check it out here!
Let me know if that's what you had in mind. 😊
Thanks so much for sharing those steps with me, Matthew. I'm seeing the exact same problem you're seeing. I agree with you that this is rather problematic, especially since settings are carrying over into new files. I'm going to bring this to my team now.
As soon as I get an update, I'll share it here. Thanks again for bringing this to our attention!
Hi Matthew,
Thanks for your reply. Yes, i have published the course after changing the settings, still it automatically revert back to its original settings that is Passed/Incomplete.
Hello group, I was about to send a client a simple LMS test file created with SL 360. I, too, noticed that the "Report status to LMS as:" setting always reverts back to the default "Pass/Incomplete" option. I was intending on using the option "Completed/Incomplete" since this doesn't involve any scoring, and thus there's nothing to "pass".
I'm hoping that changing this each time I publish still carries over my "Completed/Incomplete" choice, and that it's just reverting when I next want to publish. I can deal with that in the short term.
Hopefully the Articulate team gets this resolved before too long. This would certainly mess up a real project where one is making edits/changes and re-publishing/re-delivering to a client.
This is using the latest version: "April 2, 2018 (Build 3.14.15225.0)"
I also see that the identifier doesn't remain changes after I edit it and publish it. It regressed back to a previous identifier. This is also in the "Reporting and Tracking Options" dialog box.
I'll submit an issue.
Thanks for reaching out to our support team Scott.
Looks like Miker was able to respond and has shared your findings for us to further investigate.
Thanks for the note, Leslie.
The file this happened with happened was a "converted to SL360" file. I had used that as a starter file . Even though SL360 converts the file when you open it, etc., I wondered if there was some sort of "legacy" effect, where the file was retaining some LMS settings from its earlier SL2 version. I figured I should re-test this and start with a blank, new SL360 file. It turns out that the issue is still present in that case - I just wanted to eliminate that as a possible strange scenario where my issue only happened if opening a SL2 file and using it as a starting point.
However, it did show me something that may be close to the matter at heart: New files use the previous file's LMS publish settings. When file A has an updated setting for "Report status to LMS as:", it doesn't retain that choice when I go back to the Reporting and Tracking screen. But when I create a totally new file, file B, and go to the Reporting and Tracking screen, I see file A's settings. And then file B will not remember any new choices I make.
I appreciate the additional notes from your testing Scott. I'm going to add this as a note to your case.
Are people finding that it keeps the settings that you change when you publish it? I'm trying to get something to actually report a failure to the LMS, but it won't register as anything other than "incomplete". So I'm wondering if this bug is actually NOT changing it even when I choose to do so? Is there any word on when this will be fixed?
Great news, folks!
We just released another update for Articulate 360, and you can check out the new features and fixes in the release notes here!
One of the fixes addresses an issue in Storyline 360 where: when publishing an LMS course, changes made to the reporting options (identifier, reporting status, etc.) would not always save.
You can take advantage of this fix by updating your software to the latest version. Let us know how you make out — either here or by reaching out to our Support Engineers directly!
Nice work, Articulate team! I've updated and given it a test swing; the items that I and others had found are now acting as one would expect. The settings remain after publishing, and after closing & exiting a file. Excellent!
Hello
I have noticed that my Storyline 3 course which is has the publish settings for the results slide of passed/failed and HTML5/flash fallback is reporting incomplete/passed instead of failed on our LMS.
Is this a bug in Storyline 3 as well?
Thanks
Amanda
Hi Amanda,
What LMS are you using? Have you looked at testing in SCORM Cloud to compare the output? I'd also suggest when you test there and in your LMS you look at enabling LMS debug mode, as that'll help you see the data being passed back and forth. If you need help deciphering or translating that, let our Support Team know!
Thanks Ashley. We are using ESR. Weirdly when I retested in debug mode with a cut down version of the course that I tested on SCORM cloud the result recorded as failed on both systems. Very strange. Would size of course have anything to do with it?
Hi Amanda!
It sounds like the cut-down version of your file reported correctly as "Failed," but the original version of your file reported incorrectly as "Incomplete." Is that right?
Would you mind sharing your original file with us so we can try and pinpoint why that's happening? You can send it over right here.
Hi Alyssa
Yes that appeared to be the case. However, I tested it again yesterday and it is now recording as failed on ESR. It is very odd. I will keep an eye on it and if it happens again I'll send a file over.
Many thanks for your help.
Happy to hear that it sorted itself out, Amanda! If you run into this problem again, you know where to find us. 😁
This discussion is closed. You can start a new discussion or contact Articulate Support.