Engage Interaction in Storyline - Publishes as blank slide

Hi all,

I'm working on a multiple scene interaction to create customized content for different "roles" within the company.

I created a master engage interaction that contained all the roles and responsibilities. When I imported that master into the master content slide (non customized version, only content) the interaction published fine. Then I customized from there for what the different roles would need to know about the others. Some ended up with only 4 to view while others had 6 or 8 or all depending on who effects them in the process.

From my original engage interaction I duplicated using this method:

You can create multiple versions or copies of an Enage '09 interaction.  Here's how:

  1. Open your interaction in Engage '09.
  2. Click the round Articulate button in the upper left corner, and select Save As.
  3. Select a location and enter a file name for the new version / copy of your interaction.
  4. Click the Save button.

Once I had all the custom interactions I imported them into the customized .story, published, and when I viewed it the interactions were only blank slides.

I imported using this method:

1. clicked on new slide

2. chose engage

3. clicked import

4. tried importing interaction into the customized .story scenes they applied to

(when those published blank I tried to import interactions as a scene then made triggers to jump to that slide and back to customized scene)

Can someone please help me, I've tired all the troubleshooting I know.

I've even imported the original interaction into the customized.story, which is the same file name it was before customization, I just moved things around and duplicated some slides into more scenes. Now even that original publishes blank.

Thanks,

Brandy

5 Replies
Christine Hendrickson

Hi Brandy,

Might sound overly simplified, but how are you viewing the published content? Are you uploading it to a web server or LMS for testing or are you viewing it locally? Try uploading it, if you haven't already and see if that makes a difference. Some interactions really have issues if they're published for web and loaded locally.

Here's some extra information:

If you view published Storyline content on your local hard drive or send it to someone else to view on their local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features of your content to fail.
To properly test your published content and share it with others, upload it to the environment for which it was published. Please review the following article for details:
If you have already uploaded the content and tested it, are you able to share a the .story file and/or .INTR files, so I can take a look?
Thanks!
Brandy Rainwater

Hi Christine,

Thanks for the reply. I always publish as CD. Our CBT group links to the story.html file. It has always worked in the past. Once I publish it I preview it by opening the story.html file on my computer. I am able to see all the pages correctly except the pages that contain the Engage Interactions that were imported. 

I'd be happy to submit it to you for review. Just let me know how to get it to you.

Christine Hendrickson

Hi Brandy,

Thanks for getting back to me. The problem with running the .html file locally is that the interactions may not function because of restrictions. If you must view it locally and you're publishing to CD, try running the .EXE file in the published content folder.

You're welcome to submit the files to us in a support case, if you'd like. You'll be able to attach the project file (.story) on the second page. Just let me know if you need help with this. Also, if you do submit a case, please share the case details with me so I can follow the progress and update this thread.

Thanks again, Brandy!

Christine Hendrickson

Awesome, Brandy, glad to hear it!

It's really just a matter of lifting any restrictions in the Flash player and browsers. When you run it locally from the HTML file, those will usually keep you from seeing the interactions. Viewing the packaged executable usually eliminates this issue, though. I'm happy to hear this is working for you now.

I hope you have a great day!