Still unable to embed a Studio presentation within an Engage Int.

Jul 07, 2014

I am still unable to embed the entire published content from  the .swf file for certain pages and import them as Flash content in an Engage interaction.  There does not seem to be one .swf file that contains everything.  Please help!!!!

Posted Tuesday, July 01, 2014 at 7:12 AM

 I recently upgraded from Studio 09 to Studio 13. With Engage 09, I could take a published presentation and imbed specific slides from it, into specified Engage tabs, rather simply. I can't seem to easily complete this process with '13. Also, flash video and audio files are next to impossible to identify becasue they now have random file numbers instead of being identified as "slide 1, slide 2, etc." Is there something I am missing or is there a tutuorial out there that can provide me with some instruction accomplishing this task using Engage 13.

Posted Tuesday, July 01, 2014 at 1:40 PM

Jeff Kortenbosch said:

So if I get this right you published a Studio'13 course and from the published content you would grab the .swf file for certain pages and import them as Flash content in an Engage interaction? (You are correct)

Sounds like that should still work If the file names are giving you trouble just create a separate Presenter version for your Engage interaction containing just the slides you need (I tried that). That should make life easier

Posted Wednesday, July 02, 2014 at 6:06 AM

Thanks Jeff. I have several folders for a single published presentation. Many of them contain SWF files but they don't seem to contain all of the data (slide, animation, audio, etc.). Can you identify (for me) the folder I should be importing from to insert the ENTIRE published content from a specified slide?

1 Reply
Adrian Dean

Hi Roy,

Sorry for the late response here. Studio '13 published outputs require everything in the output folder in order to work correctly. Studio '13 does not publish to a single file such as one individual SWF.

So at this time, inserting a Presentation into Engage is considered a feature request.

Always Happy to Help,

Adrian

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