lmsAPI Functionality in HTML5 Output

No problem!  Try this:

function findLMSAPI(win) {
if (win.hasOwnProperty("GetStudentID")) return win;
else if (win.parent == win) return null;
else return findLMSAPI(win.parent);
}

var lmsAPI = findLMSAPI(this);
lmsAPI.SetReachedEnd();

For #1 and #2, I originally thought the same thing.  For example, you should just be able to call lmsAPI.GetStudentID() to get the Student ID.  However, this wasn't working when launching from HTML5 for some reason.

After lots of testing and guessing, I found a solution.  Turns out the reason why it wasn't working was because lmsAPI wasn't actually set up as a variable like it is when you use the Flash version. (Still not sure why this is, honestly.)  But, you can use the following line to get the same functionality from lmsAPI, providedyou are actually launching from an LMS:

var lmsAPI = parent;

I actually ended up creating a function for myself to use, to error-check a little bit:

function findLMSAPI(win) {
 // look in this window
 if (win.hasOwnProperty("GetStudentID")) return win;
 // all done if no parent
 else if (win.parent == win) return null;
 // climb up to parent window & look there
 else return findLMSAPI(win.parent);
}

function someOtherFunc(){
 var lmsAPI = findLMSAPI(this);
 if(lmsAPI != null){
   //do stuff
 }
}

Hi Helene,

SetStatus("completed") only works with the Flash version because the HTML5 version doesn't end up using the lms.js file. So, you will have to bypass that function and directly call the function that the SetStatus function would have called... Try this:

function findLMSAPI(win) {
 if (win.hasOwnProperty("GetStudentID")) return win;
 else if (win.parent == win) return null;
 else return findLMSAPI(win.parent);
}

var lmsAPI = findLMSAPI(this);
lmsAPI.SetReachedEnd();

OK so I tried this

---------------------

var player = GetPlayer();

function findLMSAPI(win) {
// look in this window
if (win.hasOwnProperty("GetStudentID")) return win;

// all done if no parent
else if (win.parent == win) return null;

// climb up to parent window & look there
else return findLMSAPI(win.parent);
}

var lmsAPI = findLMSAPI(this);
var myName = lmsAPI.GetStudentName();
var array = myName.split(',');
var newName = array[1] + ' ' + array[0];
player.SetVar("newName", newName);

-----------------------------

And it works!

Thanks so much

Chris

Hi Amit,

I would try replacing all instances of  SetStatus("passed");  or  SetStatus("failed");  with one of the following:

lmsAPI.SetPassed();
or
lmsAPI.SetFailed();

This should call the correct function directly.

I don't have much experience with Moodle, so I'm not sure what the problem would be.  Are you publishing to SCORM or AICC?  I've only tested my code with those tracking types.

The only other thing I could think of is that the lmsAPI is not the 'parent' object, but is instead up a parent level or two.  That's when I would include the findLMSAPI function I wrote in the comment above instead, since it recursively looks up one level at a time, trying to find the lmsAPI.  In which case, you would replace:

var lmsAPI = parent;

with:

var lmsAPI = findLMSAPI(this);

---

If this still isn't working, I would start using Developer Tools to determine the root of the problem.

Hi Stephanie,

Thanks for checking in. This is something that our team is still taking a look at. Those features and Javascript elements that were accessible in Storyline 2, changed in Storyline 3 and 360 as we entirely rewrote the player and it's behavior. 

Those types of modifications have always been unsupported, but we do see the value in their use, so we're looking at how and why they fit the needs of Storyline 2 users and what options we could include in Storyline 3/360 to fix it going forward. 

Hi Ashley,

I understand that the modification of Javascript is not necessarily "supported" by Articulate.  That makes total sense, since it's not on your team if one of us makes a mistake in our coding.

However, in most cases I've encountered related to this topic, I believe we are only modifying the code because of a lack of a feature that meets our needs within Storyline.  

For example, this entire thread probably wouldn't be necessary if there was a trigger for "Mark Course Complete" within Storyline.  In that case, I would be able to simply say "Mark the course complete when the timeline starts on Page 4.4" or something to that effect.

Since this feature would be built into Storyline, it would presumably work in both Flash and HTML5, and wouldn't require external Javascript.

Alternatively, it could also be solved if we were given a new option in Publish Settings > Tracking, for "Mark [Completed/Passed] when user reaches slide: [4.4]".

I hope this is helpful for your team in determining how best to approach the request.

Hi Shane,

Thank you for the kind words!  My guess is that you might be using a "Passed/Failed" instead of a "Completed/Failed". 

I would recommend trying to call the following instead:

lmsAPI.SetPassed();

If you are looking for the different options you should be able to use with lmsAPI, here is the switch statement in the lms.js code, which I used as the basis of the code I wrote:

switch (strStatus){
   case "complete":
   case "completed":
      lmsAPI.SetReachedEnd();
      break;
   case "incomplete":
      lmsAPI.ResetStatus();
      break;
   case "not attempted":
      break;
   case "failed":
      lmsAPI.SetFailed();
      break;
   case "passed":
      lmsAPI.SetPassed();
      break;
}

Good luck!

Adam Trosper, you sir are a genius! I actually whooped when your suggestions worked, as I've been trying this for months without success and just happened across your post today!