16 Replies
Ashley Terwilliger

Hi Steve, 

Engage 09 didn't include HTML5 support - so you won't be able to view it within the iPad in mobile safari or the mobile player app. If you have Engage '13 (or even want to use the trial) you could update the interaction and insert that into Storyline. Please note that you can't have Engage '13 and '09 installed on the same system - so it will remove Engage '09 but you can always reinstall after the fact. 

Ashley Terwilliger

Sorry Steve - I totally misread that! For Engage '13 content you'll want to review the information here in regards to setting it up for HTML5 deployment.  Since you import in the Engage file into Storyline normally it loses the file's ability to determine to show the HTML5 so that article will walk you through the steps around it. 

Also, double check that you're using the latest update of Storyline and Engage - as they both included fixes dealing with iOS9. 

Ashley Terwilliger

Hi Steve,

First, I wanted to let you know that responding via email includes your signature here - so you may want to edit the post to remove that information.

Were you able to open the article that I attached above? Here's the relevant snippet: 

When you use this automatic import method, Engage interactions are embedded as Flash objects. As a result, they aren't supported in HTML5 output or the Articulate Mobile Player app. See also:

So that would prevent you from seeing them in iOS9 or earlier regardless. If you need to embed them in your Storyline course, you'll want to publish first in Engage (using the latest update 7) and then host that published content on a web server that you can link to in your Storyline 2 course as a web object. Also make sure you're using the latest update of Storyline 2 (also update 7) to publish as it offers support for iOS9. Directions on how to set this up are include in the previously linked article. 

Hope that helps clarify and please let us know if you need anything else! 

Steve OConnor

Ashley,

 

Thanks - You've put me on the right track now. I have Storyline 2 (just purchased Oct 22) so I have the latest one and a new user. I've read the links above but most reference importing & editing. I need the specific steps in linking to the Engage as a web object. I changed the Engage player browser settings to 'launch player in new window' and published but need steps from Storyline slide to link to it. Am I getting there? Thanks.

Ashley Terwilliger

Hi Steve,

Sure the directions on linking to the Engage as a web object are below:

  1. First, publish your Engage interaction for web.
  2. Open the folder where the published output is located and rename interaction.html to index.html.
  3. In Storyline, navigate to the slide where you want to embed the interaction.
  4. Go to the Insert tab on the ribbon and click Web Object.
  5. Click the Open Folder button at the right end of the Address field.
  6. Browse to the folder that contains your published interaction and click OK.
  7. Click OK again to insert your web object.

You could also place the Engage interaction on a web server and use the URL to link to a web object following these directions linked here. 

Ashley Terwilliger

Hi Steve, 

I guess it depends on "right" for what...? :-) 

The "launch player in new window" is generally specific to an LMS setting or for when the user clicks on the link in the window and it needs to launch in a new window. If you want it to appear within the Storyline interface, I may not select that option and then just embed directly into the Storyline slide. I would definitely display it with no browser controls though - that way it'll appear more seamless with your Storyline slide. 

Ashley Terwilliger

Hi Steve,

The published Engage output will have a file with interaction.html and that is the file that needs to be renamed to index.html. Once you've done that, you'll use that file to link it within your Storyline course, prior to publishing, as a web object.  You'll also want to make sure that once you've published the Storyline file, you're uploading the entire published output folder to your web server or LMS - testing it locally may not allow the web object to play. If you're not ready to place it on a live site you could look at using one of the options mentioned in this article.