Storyline 360 to SharePoint

Also having issues with running Storyline 360 content on SharePoint. A while back I tried renaming story.html to story.aspx. The file runs on SharePoint, but because the code in story.html checks browser type and availability of Flash, it eventually redirects to story_flash.html or story_html5.html. At that point, SharePoint wants to download one of those HTML files.

I renamed those two files to have an ASPX extension, and then opened story.html in Notepad and easily found the references to story_flash.html and story_html5.html, changing those to look for the renamed ASPX files...

And it works! Not too much work to get things running on SharePoint. However...

I then ran into issues with imported content from Engage. Like Storyline, Engage publishes a handful of HTML files, which SharePoint insists on downloading.

So, I found all those files (a bunch, because I love the rapid development I can do with Engage interactions!!!) and renamed them to have an ASPX extension. And, without getting into the gritty details, I had to use Notepad to go into the code and changes references to the HTML files over to ASPX.

No luck this time. It appears that published Engage interactions seem to use JavaScript, CSS, and XML to generate the URL used in the slide frame in Storyline for the interaction. (okay, I got gritty there for a second)

The bottom line is, the Storyline content runs just fine (with either Falsh or HTML5) but the interactions result in a 404 page not found error.

I haven't tried, but I suspect the same might be the case for content developed in QuizMaker and imported into Storyline.

Yes, I could recreate my interactions in Storyline, but I like Engage.

I asked the SharePoint admin to see if they could just make an adjustment on the server to allow the running of HTML files, rather than forcing a download (Save/Save As) but IT security won't allow that to happen. 

Anyone experiencing this issue? Any clues? Seems like this could be a feature request to allow choosing HTML or ASPX as the output "wrapper" format... or even a SharePoint tab on the Publish page options. ;-) 

Thanks,

John