Unable to Aquire LMS API...Can I link to story.html?

Aug 09, 2013

Hi Everyone!

I have a module in which the client needs an option for simple HTML content. What I have done is created an HTML module in Trivantis Lectora, and on the first page of this module I have a screen which says:

"Choose the Flash option if your system supports Adobe Flash. If your system does not support Adobe Flash, then please choose the Non-Flash option."

So, if they choose the Flash option, it takes them to the module proper, which of course is entirely developed in Storyline. If they choose Non-Flash, the HTML section basically just presents them with some download links for resources and then gives them a quiz.

My problem is that when I try to link to the index_lms.html in the storyline published files, I get an error about being "Unable to Aquire LMS API."

When I link the HTML page to story.html instead of index_lms.html, it works fine. So my first question is, can I open the Storyline module from story.html and still have it track and report to the LMS properly? I'm guessing probably not, but I'm not sure what else I can do...?

Thanks for any help you can provide!

1 Reply
Justin Grenier

Good Morning, John.

Linking to index_lms.html from an HTML page in another course will probably not allow your LMS to connect with your content in a way that allows for proper communication between the two.  You might be able to ask your LMS vendor if there is a way to make this work.

On the flip side, story.html, when launched directly, does not attempt to communicate with the LMS at all.

What do you think of the following alternative approach?

  • Create all of your content in Storyline.  Retain your "choose your own adventure" slide at the beginning of the course, and keep both the rich and the non-rich content in Storyline, branching to them from the first slide as appropriate.
  • Include HTML5 output when publishing.
  • Launch the index_lms.html file directly from within your LMS.  If the learner is using a non-Flash compatible browser, they'll see the HTML5 output.  This isn't quite simple HTML, but it sounds like both the "choose your own adventure" slide and the resulting download links/resources/quiz might be simple enough to avoid any major lack of browser support for the HTML5 standard.

Do you think that might work?  Good luck with your project!

This discussion is closed. You can start a new discussion or contact Articulate Support.