"Exit Course" button not working
Aug 22, 2014
Hello, all.
About a month ago, I installed the update to Storyline (6.1407.2208) and since then have not been able to get "Exit Course" buttons to work on my last slide so the learner does not have to wait for the music trailer to fade off and let the course close by the Player when the Timeline ends.
I use the Insert Button feature, name the button "Exit Course", and set up a trigger to Exit Course when the User Clicks.
It does not work in the Preview Mode, nor in the Published Product. Yet, before the upgrade, the use of such buttons worked just fine for me.
Did something in the Upgrade interfere with how the trigger works?
22 Replies
Hi Richard,
I don't believe anything has changed for Update 6. The exit course trigger has been a known issue, usually caused by circumstances out of our software and it's published output's control. Please take a look at the following article for reasons why it may not work and suggestions on how to make it work moving forward.
Let me know if you have any additional questions.
Always Happy to Help,
Adrian
Thanks, Adrian.
You the man! I now have a simple workaround... New Window.
Hi Richard,
Glad to be of help!
-Adrian
Couldn't agree more Richard.
Hi Adrian,
I have a Storyline file with an Exit button. The player is set with "Launch player in new window" checked.
I published the course on Google Drive.
The Exit button does not work in Google Chrome, but works in Internet Explorer.
I published now the same file on our website and have the same behavior.
The Exit button does not work in Google Chrome, but works in Internet Explorer.
Anything I can do to ensure the same behavior of the Exit button in the course published on our website, regardless of the browser? I do not know what browser each learner will use.
Thanks very much,
Mihai
Hi Mihai,
Unfortunately, there aren't any other methods than those mentioned in the link I referenced above. Did you add a target attribute to your link on your website?
An important thing to note though, is that whether the user leaves the course via the exit button or by closing the browser window, the result will be the same.
You might be able to do something with JavaScript that will allow the Window to close, but it may not work, given the issues our exit course trigger can have. In any event, if you go that route, it will be unsupported by us here at Articulate. You are welcome to seek any JavaScript help here in the forums, if you like.
-Adrian
Hi Adrian,
Thanks for the prompt reply. I don't know what a target attribute is, I'm a just doctor for humans not for computers :-( To my knowledge, it's a simple URL link to the story.html file. I can share with you privately if needed.
Anyway, this is not a problem related to the website, since the same Exit works in Internet Explorer but does not work in Google Chrome, regardless of the site where it was published.
I am happy to keep the course on Google Drive but I still need the Exit to work regardless of the users' browser. Can you help?
Thanks,
Mihai
Hi Mihai,
In the link I referenced above and here in this post, it goes over how to add a target attribute to your link. The thing to keep in mind, is just because it works in Internet Explorer, does not mean that additional steps won't need to be taken to get it working in the other browsers. Each browser is very different under the hood, not just in appearance. So please see about adding a target attribute to your link from your website, just to see if it resolves things for you in Chrome.
Beyond the target attribute and my JavaScript suggestion, there are no other methods for getting the exit button working at this time. You could put wording in your content that would tell the user that they will need to close the new window if the exit button doesn't work, or you could do away with the exit button all together to eliminate any confusion. You also would have the option of using JavaScript to trigger a pop-up window which would allow you to say the same thing as the actual text on your slide, if needed.
-Adrian
I'm seeing this issue in Storyline 2. The following JavaScript worked for me when trying to close the course in Chrome:
Trigger: Execute JavaScript
window.close();
Hi Robert! This thread is a bit dated, but we do have some documentation for Storyline 2 as well.
When you use the "Exit course" trigger, you may find that it doesn't function as expected in your published course. See this article for reasons and solutions.
Thanks for this Leslie. I was looking for a solution that wouldn't involve altering the configuration file. My fear is that the configuration file will get overwritten every time I install a Storyline update.
Your fear would be correct Robert. Have you reached out to your LMS to see if this is a setting that can be altered so the recommended standard setting would still work?
I have tried both the options
1. Launch player in new window (creates launch page).
2. Updated the .js file "Configuration.js" and tried it LMS.
I am having the same issue exit button not working as intended.
Hello Rajesh!
Sorry to hear that you've run into difficulty with this as well.
Are you able to replicate the issue in SCORM Cloud or is the issue only happening in your LMS?
Not sure if you looked at all of the options in this article that was shared above.
Actually the LMS which I am using is success factor. I have published the course as SCORM package.
I apologize for any confusion Rajesh. SCORM Cloud is an industry standard that we use for testing. It helps us identify if an issue lies within the project or the LMS. You can read more about that here.
Thank you.. I think SCORM cloud is similar to ADL test suite.
I will go ahead and test my course with SCORM cloud.
Thank you..
Thanks, Rajesh. Keep us posted on how it goes!
article
Having a similar issue that your above mentioned article doesn't cover.
When you click the "Exit Button", the course closes, but the window stays open. and says "Please wait. Loading..."
Any advice on how to get the window to actually close. I have tried updating the config file. Nothing seems to work.
If I set it to open in a new window, it opens 2 new tabs. a launch page first opens, then the course and when I exit, the course closes but leaves the launch window open.
Hey Brett!
So, it sounds like the window you are in, which is the course, is closing as expected. You were hoping this would close the initial launch window as well?
I'm not aware of a way to set that up, but hopefully someone in the community will be able to chime in if they've achieved this task.
Scenario 1: Changing settings in Player Options to open in a new window.
Result: When course opens, it opens a new tab (launch window), then launches the course. Clicking Exit button closes course, but leaves launch window open.
Scenario 2: Leave Original settings of opening course NOT in new window.
Result: When course opens, it opens in new tab (no launch window/tab). Clicking Exit button closes course, but not the actual window or tab that the course was open in.
Either way, there is a window/tab left open after clicking Exit Course. Not exactly the results any of us should be getting when using an Exit button. Don't you agree?
I understand Brett, and yes I do agree. Looks like you linked to our support article, so you are aware that this is a browser limitation.
This discussion is closed. You can start a new discussion or contact Articulate Support.