Failed Score Not Allowing User To Exit Course On LMS
I know this most likely is not a Storyline issue, but I thought I'd check to see if anyone has ever came across this problem. I have a published Scorm 1.2 file with one result slide set to 80%. The report status to LMS is set to pass / fail. The results slide appears at the end of the assessment and is working properly. After viewing the Results slide the user clicks next and views a "conclusion" slide where there are two exit buttons. One is a hotspot over "exit" text and the other is the Exit within the player.
When published to our LMS (SmartPros) everything works like a dream if the user passes the course at 80% or above. The passing score is sent to the LMS and the user can exit the course by clicking any of the two exit options.
However, if the user fails the course the results slide reflects the correct failed score and allows the user to continue to the next slide by clicking the next button. This is the "conclusion" slide where the user can select the hotspot with a trigger exit this course or the exit function within the player. When the user fails the exit functions disable and the failed score will not report to the LMS. It reports as course incomplete.
Here are some items we've tried to fix the error:
Manipulated the published JS file exit behavior to ALWAYS_CLOSE and then to ALWAYS_CLOSE_TOP
Changed the triggers on the results slide to submit results on when timeline starts for the first layer AND on the failed and success layers.
Changed the trigger for submit results to be attached to the Next button and also an Exit button.
I have also deleted the remaining conclusion slide so that the results slide is the last slide in the course.
Unfortunately, we have found no fix to the issue. We have conducted multiple testing sessions with about six users at a time. We have tested on Mac and windows based machines and have used Chrome, IE, Firefox and Safari browsers. We get the same issue with the failed score not allowing user to exit each time on all variations of systems and browsers.
On another note, it works absolutely perfect on Scorm Cloud. So that tells me that this is our LMS issue, but we've received very little help or support. So I am crossing my fingers that someone out there has any advice or guidance to give.