Embedding Articulate Engage interactions in Storyline

Mar 26, 2019

Duncan Hamilton
By Duncan Hamilton

This problem is a bit strange, so bear with me.

Normally, importing Engage interactions into Storyline is a simple process. However, the LMS I am currently using has a strange issue with embedded Engage interactions. Namely, if the Engage interaction link ends with .html, it won't work (it will actually embed a completely different Storyline file that is stored on the server, but that's an LMS issue).

The strange thing is that this module contains a two different Engage interactions, and one of them works perfectly fine. The one difference I can identify between the two is that when "Edit Web Object" on the interaction, they both display different adress's. One has "...Temp\Articulate\Storyline\6LByjddaGL1\engage.html" and the other has "...Temp\Articulate\Storyline\6ouxl6kFqJJ"

I know why these two are different, as they were uploaded by different people. What I want to know is why does one have a .html filename at the end and the other does not. I believe the .html filename is the being interpreted poorly by our LMS.

Is there a way to embed Engage Interactions that I am missing? I have tried importing the Engage file, as well as publishing the Engage file and then importing it. Both have the same problem.

11 Replies
Katie Riggio
5 years ago03/26/19 at 8:30 pm (UTC)

Welcome to eLearning Heroes, Duncan. We're here to help!

First, the import process you took is spot-on. I'm having trouble recreating this in a Storyline 360 test file (here's a quick Peek 360 recording of what I see), so I'll need your help:

  • Are both Engage interactions saved on a local hard drive? Saving to a network or zip drive can cause issues similar to what you're experiencing, so I like to rule this out as the culprit.
  • What version of Storyline and Engage are you using? 
  • With your permission, I'd like to test your .story file to get a clear picture of what's happening. If that works for you, here's where you can share the file privately with me. I'll let you know what I find, and will delete it after troubleshooting.

Looking forward to our next steps!

Duncan Hamilton
5 years ago03/26/19 at 9:02 pm (UTC)

Hi Katie, thanks for the quick reply.

The Engage interaction that is causing the problem was uploaded from a local hard drive, I'm not sure how the one that does work was uploaded, which is what I'd like to get to the bottom of.

Both Storyline and Engage are up to date (v3.25 and v4.21). I'm fairly certain that this is an LMS problem, not a Storyline problem, but if there is a temporary work around it'd be nice.

I will request permission to share the Storyline file with you and hopefully you'll be able to see what differentiates the pair of Engage interactions.

Thanks!

Ashley Terwilliger-Pollard
almost 5 years ago04/24/19 at 2:09 pm (UTC)

Hi Duncan,

Our team is sending emails to the same email address you've used to log in here to the E-Learning Heroes community, and that's associated with your Articulate 360 subscription. Were you able to check that the emails are not being redirected to your Junk/Spam folder? Can you reach out to your IT team to have them allowlist the email address of Support@articulate.com? 

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