Forum Discussion
Engage Interaction still generates .swf in Storyline web output
Our content management system validates output content that we upload to block anything with Flash (.swf). While we don't built as much with Engage as we used to, we have discovered that when we add an Engage interaction into a Storyline project, then export as Web output, our CMS rejects it.
Poking through the zip file, we discovered a TON of .swf files lingering in there.
WHY?? We're well beyond the world of Flash now. HTML5 rules, right? Why does .swf need to be in there? We have validated that we are using the latest versions of Storyline and Engage 360.
In our research and testing, it appears that Storyline adds this, as the Engage content on its own doesn't seem to contain the swf when it is exported separately without Storyline involved. Any plans for Articulate to address this?
We can't maintain existing Engage content because our IT department refuses to remove the Flash validation on the CMS for security reasons.
Just for fun, we tried putting the Engage interaction into Rise and exporting the web output there. Same result.
Hi, all!
I have some great news to share! We just released a new version of Storyline 360 (Update 102), which included a fix for the issue where SWF files are created after publishing an embedded Engage interaction in Storyline 360.
To take advantage of this update, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find step-by-step instructions here.
Please let us know if you have any questions by posting here or reaching out to our Support Engineers directly.
9 Replies
This is great news. Thank you for addressing this important issue!
Hi, all!
I have some great news to share! We just released a new version of Storyline 360 (Update 102), which included a fix for the issue where SWF files are created after publishing an embedded Engage interaction in Storyline 360.
To take advantage of this update, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find step-by-step instructions here.
Please let us know if you have any questions by posting here or reaching out to our Support Engineers directly.
I'll have to see where to find that. My hope is that they'll at least address this one issue with a final update!
Hi MichaelDixon-e1,
We released an update way back on May 4, 2021, that removed all Flash files from Engage 360 interactions. Courses published using the most recent versions should no longer have Flash content included in the published output. Would you be willing to share a copy of your project files here or in private by opening a support case so we can check for any Flash files? We'll delete it when we're done testing!
Actually, after submitting this to e-learning heroes, I submitted a support request with project files and received a response indicating a team was assigned to the issue. Apparently v.99 of Storyline does behave properly, but other versions seem to generate .swf, so they are working on the issue and potential fix.
Engage indeed is not generating .swf, but when Engage is added to Storyline and a Web output is generated, that's when .swf appears...so it's a Storyline issue.
I would raise a support case, Engage is no longer actively developed but this should be fixed.
Has Articulate indicated they will no longer develop the product? I mean, they did release 64-bit support for it not long ago.
They announced they will no longer get actively develop Studio a while back.
