At the end of a module I created, there is an exit button that is supposed to complete a couple of different actions when it is clicked. These actions are as follows: "complete course as completed/passed when the user clicks button" and "exit course when user clicks button". When I run the entire module within Storyline, the exit trigger works every time. I am led to assume that the "complete/passed" trigger works as well, but I cannot determine that within the storyline preview. When the module is published to the LMS, as a SCORM 2004, 2nd edition file, the "complete/passed" trigger seems to work, however it is not being communicated since the pop-up window will not close. This tells me that the exit trigger is not working once it is published, or that is just isn't communicating with the LMS properly. Other courses with this same set of triggers work flawlessly. Is there anything that I can change on the Storyline side to try and fix this issue? Any help would be GREATLY appreciated.
If you have other courses which use the same configuration and publishing settings that work in your LMS, then the issue might be something that's specific to the affected course.
We'd first recommend testing how your course will behave in a different LMS to see if the behavior is isolated. Here's how you can test your course in SCORM Cloud. If your course works as expected in SCORM Cloud, then the issue might be specific to your LMS. Additionally, you can also enable the LMS debug logs for your course which will help determine if the exit button in your course is sending the correct signal to close out the course when pressed.
If you're open to a redesign, this article has some alternative solutions to closing out a course which you can explore:
If you are able to replicate the behavior in SCORM Cloud, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
1 Reply
Hello Grant,
Thanks for reaching out!
If you have other courses which use the same configuration and publishing settings that work in your LMS, then the issue might be something that's specific to the affected course.
We'd first recommend testing how your course will behave in a different LMS to see if the behavior is isolated. Here's how you can test your course in SCORM Cloud. If your course works as expected in SCORM Cloud, then the issue might be specific to your LMS. Additionally, you can also enable the LMS debug logs for your course which will help determine if the exit button in your course is sending the correct signal to close out the course when pressed.
If you're open to a redesign, this article has some alternative solutions to closing out a course which you can explore:
If you are able to replicate the behavior in SCORM Cloud, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!