Everything we know about Cornerstone on Demand and Storyline!

Hi Will,

You'll need to modify the original .story file and republish, but I don't think you'd need to create a whole new file - you may want to follow the steps here in regards to adding the question slide and track based on that one slide with the modifications you'll make to the publish settings. 

Hope that helps - and I'll defer to the community in regards to how to upload or modify within Cornerstone. 

Rachel, I've seen that left-side menu with two different clients using Cornerstone. It's specific to SCORM 2004 and related to a back-end setting that they need to change for you. In my experience, they'll say it's a content-specific issue, but it's not - you just have t be persistent.  =) I think a lot of the support people at CSOD don't know about it, so they have to research how to fix it. But it can absolutely be fixed by them changing that back-end setting (I don't know the name of it).

Hi, B K - 

I've had success running the HTML5 output. The new SL360 provides the option to just publish to HTML5 without the Flash publish.

If you're having trouble in IE, give this a shot. In the General tab of the catalog properties page for the online class LO, make sure compatibility is turned off. 

Can anyone tell me how to publish and then what to check in the compatibility or other options to get content from Storyline 1 to appear correctly in the Cornerstone Mobile App for iPhone? I am using SCORM 2004. I can get the audio to appear, but none of the images or text show up--not even the resume buttons on the resume pop-up. The attached image shows what it looks like.

Hi, Chris - 

Don't use the Articulate Mobile App in your publish. It will not communicate with SCORM. Publishing to HTML5 should get it to run. You'll want to test. HTML5 doesn't run equally on all devices in SL2 publishes. SL360 offers improvements.

Tracy, maybe try using a URL shortening service such as https://goo.gl/ as a workaround?

Hi Chris, I'm not sure what the explanation is for the bandwidth.

One thing I'd share with you, is whilst you can launch videos directly from CSOD, once it's been watched a learner will have to 'mark as complete' to record this in their learning records. If the video was part of a SCORM file this would automatically show as completed, based on your publishing settings.

Akamai is serving up video at a lower bitrate. If you played the video from a different device / connection, you'd likely see a lower bitrate coming from Akamai's servers. Storyline's bitrate is fixed based on how it's compressed in publish settings. You can adjust the bitrate settings a bit in Storyline's published output. 7MB/s is high. 

There are also ways to control bitrate by compressing your video to the rate you want it before import into SL and setting the properties of the video to not recompress on publish.

There's a possible way to get this done using a bit of Javascript, a variable in Storyline, and a trigger to pause the timeline. If you're not comfortable with Javascript, it could be daunting to implement.

The script is described in this stackoverflow post:

http://stackoverflow.com/questions/1060008/is-there-a-way-to-detect-if-a-browser-window-is-not-currently-active

You'd want to trigger something that incremented a number value in a storyline variable then use a "when variable changes, pause timeline" trigger.  This would let the browser window detect when focus is lost or the window goes into the background.  In a Javascript trigger that fires when the slide loads that you want to have the video pause:

var hidden = "hidden";

var player=GetPlayer();

// Standards:
if (hidden in document)
document.addEventListener("visibilitychange", onchange);
else if ((hidden = "mozHidden") in document)
document.addEventListener("mozvisibilitychange", onchange);
else if ((hidden = "webkitHidden") in document)
document.addEventListener("webkitvisibilitychange", onchange);
else if ((hidden = "msHidden") in document)
document.addEventListener("msvisibilitychange", onchange);
// IE 9 and lower:
else if ("onfocusin" in document)
document.onfocusin = document.onfocusout = onchange;
// All others:
else
window.onpageshow = window.onpagehide
= window.onfocus = window.onblur = onchange;

function onchange (evt) {
var v = "visible", h = "hidden",
evtMap = {
focus:v, focusin:v, pageshow:v, blur:h, focusout:h, pagehide:h
};

evt = evt || window.event;
if (evt.type in evtMap){

player.SetVar("yourNumberVariable",Number(player.GetVar("yourNumberVariable))+1);
}

}

// set the initial state (but only if browser supports the Page Visibility API)
if( document[hidden] !== undefined )
onchange({type: document[hidden] ? "blur" : "focus"});
}

It should. I believe the event listens for any focus event. So if the popup loses focus to another application, it should still fire the event. Haven't tested in awhile but I believe this is the way it worked with the blur:focus event. I'd expect the page visibility API to be an improvement since blur:focus is only used as a fallback.