Everything we know about Cornerstone on Demand and Storyline!

Hi, Amy - 

To report survey and question results, you'll need to add a results slide and associate the items with the results. You'll also need to track the completion to the results slide if you want to be able to record the interactions to the LMS. 

This is no good if you want the survey to be optional, yes? Here's where you get into workaround territory. One way --maybe the only way-- to get this done while still leaving the desired results tracking is by using a little bit of Javascript. 

If this is something you're comfortable trying, I'll post an example and explanation of what's going on. It involves script to:

• Suppress the default Storyline behavior and prevent SL from overwriting our manual completion.
• Sending completion based on the logic that you want. This is either by adding triggers to check an existing results slide or by firing a JS trigger when a slide is reached. 
• Associating the publish settings with your survey so that Storyline passes each interaction to the LMS.

This is something that gets a little bit easier with an LRS in place as all Tin Can API interactions will be reported to the LRS regardless of how the publish settings are configured. 

I think I figured it out - the Responses number goes down each time because one set of learners only had to take the entire quiz 1 time (passed on the first attempt), another set had to take the quiz 2 times, and the third set had to take it 3 times. Thats why it is always 40, 11, and then 1 for each question (29 passed it the first time, 10 the second time, and1 the last time).

Hello,

I just wanted to provide a helpful tip that I just discovered. If you are publishing to CSOD and your Articulate course content is not showing, or showing as a blank screen a solution I found was to uncheck the selection box that states "When running in LMS, ignore Flash cookie" this box is found in the "Player Properties" window.   This box, once unchecked will allow your course to play on mobile devices in the CSOD application.

Hi Will, I share your pain. This is a common issue I've come across and it's not a Storyline issue - plenty about it online if you Google it.

Any material we've created, whether it be a SCORM file, PDF or otherwise behaves in exactly this way since an update to Google Chrome which makes all links open up in the existing window in a new tab, thus appearing over the course so our employees think they have lost the original course window.

Is there a magic fix that can be put in place in Google Chrome that solves this for multiple software? I couldn't find an answer, but it would be nice to at least solve it for Storyline files. (Our old Storyline 1 files work fine and are not overridden by Google Chrome)

Also it's worth noting if users opt for Internet Explorer instead they all work as intended.

If someone has cracked this I'd love to know too!

Ben and Will - I was getting the same error message with uploading to CSOD. I unzipped my Rise SCORM file and discovered two JavaScript files with the same name in one folder (player-interface.js). I deleted one of the player-interface.js and then rezipped the SCORM package. I was then able to successfully upload the Rise course to CSOD. I assume this is a publishing bug with Rise. 

Is anyone able to confirm that this is in fact a publishing issues with publishing Rise courses to SCORM?

Thanks Will and Julie for that info - I gave it a test with a Rise course I had which included a Storyline block and I didn't have an additional player-interface.js file. Here's a screenshot of the same spot in the Assets folder you mentioned:

Could you share a copy of your Exported Rise zip with me, so I could take a look at that one? Also, I'll test uploading it to SCORM Cloud to see how it behaves. 

The JS is pretty straightforward. We've been using similar to the below for awhile. HTML5 references the lmsAPI differently than the Flash output. A conditional check to see if a function exists typically helps send the calls in the right direction. 

var player=GetPlayer();

//status is pretty simple.
SetStatus("completed");

//if you also want to set the score.
lmsAPI=parent;
var tPercent=player.GetVar("SLSCORE"); //grab a score variable from storyline

if(lmsAPI.hasOwnProperty("SetScore")){
lmsAPI.SetScore(tPercent,100,0);
}else{
SetScore(tPercent,100,0);
}

While we have used close course triggers in the past, we have found the most reliable way to get learners out is to just instruct them to "You have completed the XXXXXXX close the course window by clicking the 'red X' in the upper right hand corner of the player."

I think that the triggers that actually communicate completion to the LMS are the "Submit results" trigger (if you "Track using a quiz result") and  the newer "Complete course" trigger (if you "Track using complete course trigger"). We avoid tracking based on slide views because it causes too many support headaches when someone insists they viewed all the slides and we don't have a good way to dispute their assertion. I don't think it should matter how the course is exited as long as one of those triggers is in place.

I have read through most of the Cornerstone threads here, and I am wondering if anyone ever was able to get Cornerstone to report more then 1 attempt on a SCORM quiz.  The courses work fine in other LMS's and SCORM Cloud, and it seems to be a Cornerstone only problem.  The standard reporting seems to be broken in Cornerstone.  Cornerstone has no answer and says it is a Storyline problem.  In my testing, standard reports only capture the first attempt score.  In later attempts, the report will update the pass/fail, but the score and attempt date remain the same.  If I reversion a training, it will add another line item to the report and do the same thing.  I can never get it to adjust number of attempts, and the score is always locked into whatever their first attempt was.  If I use reporting 2.0 and the field "SCORM 2004 Quiz Data - Quiz Score", I can get the most recent attempt score, but I still can't get all attempts and scores, and I can't get it to say the user had more then one attempt. Since the 2.0 report is capturing the last attempt the user does, I know the SCORM file is pushing the data to Cornerstone correctly.  I just think Cornerstone reporting is incorrect.  Anybody experience this problem and find a solution?