Storyline 360 to SharePoint

Sure, Lisa. Happy to help. Please let us know how things go with IT. 

So OneDrive is locked down on .aspx, but allows .html, gives you a security message, and then runs. At least you've discovered it can run from the server! This will be useful for IT to compare server settings for OneDrive and SharePoint.

I haven't used SL360 with an LRS, so I'm not much help there. I suspect that it's similar to using it with an LMS. 

I'd recommend using https://cloud.scorm.com to test your content before loading into an LRS or LMS. It's a great, free resource for testing content with several users. 

John

Hi Michele,

Thanks for following up. I had some success getting embedded Engage interactions to work on SharePoint, but it continues to be inconsistent.

When you embed an Engage interaction on a slide in Storyline, in the background SL publishes the Engage project and puts it into a folder in your Windows profile data temporarily, until you publish your Storyline project, at which time the Engage content gets put into a folder in the published project. If you take a look the properties of the Engage interaction on the SL slide, you can see the path, it goes to an HTML file. In order to have the Engage interaction work on a SharePoint server, you need to do a similar thing to what you do with the story.html file and renaming it to story.aspx. 

When you publish a Storyline project with Engage interactions, it puts the published files into the story_content/WebObjects folder. You'll need to go into that folder and copy the HTML files to ASPX, but... the linking to the Engage content in the published Storyline project, points to HTML files and not ASPX files... so, even if you create the ASPX files, the Storyline slide is looking for an HTML file. And we know those get a forced download from SharePoint.

What you need to do is, once you've published the entire SL project, is to copy the individual folder from the published project folder, do the HTML to ASPX copy/rename, upload that folder to a separate folder on SharePoint, make sure that works with ASPX.

After you've confirmed the Engage interaction will run on SharePoint from the folder you've uploaded, then you go back to the original Storyline project, right-click on the embedded interaction and use Web Object > Edit to change the path to the folder on SharePoint, where the working ASPX version of the interaction is stored. 

Once you've updated the path to the Engage "web object" that is stored separately on SharePoint, republish the whole Storyline project again. Do the HTML to ASPX step and then upload the updated published project to SharePoint.

Kind of a twisted approach, but it seems to work.

So, it breaks the link allowing you to right-click in Storyline to edit the Engage interaction. If you do right-click and edit, you'll need to go and find that deep folder in your Windows data again and upload that to SharePoint again. 

I would say if you absolutely need to do this, wait until the project is reviewed and approved before publishing to SharePoint.

The other thing that doesn't quite work with this approach is the ability to use the Next button while in the Engage interaction, to step through the interaction. You'll need to use the navigation built in to Engage, rather than the Storyline Next button. That will just take you to the next slide.

Hope this helps. Not an ideal solution, but it seems to work. Mostly.

John

Hello Erika!

Hopefully someone more familiar with SharePoint will be able to chime in and assist you here.

I did see a related conversation in another thread here recently. Perhaps that information will assist you as well or you are welcome to reach out directly to one of the users there for further assistance if needed.

Okay, so you in order to create an aspx file you simply change the .html file extension to .aspx?

That's my understanding based on conversations I've seen in the forums Greg, but I do not use SharePoint. You are certainly welcome to reach out to the user directly via the 'Contact Me' option on the user profile if you do not hear back soon.

No problem Greg.

It looks like your email signature came through when you replied via email. You can remove that if needed and here’s a quick Peek video if you need help.

Thanks, Ashley! Yes, digging deep!

I will definitely try publishing the Engage interactions and adding them as Web Objects, rather than just importing them. GREAT idea!!!

Glad that idea kept you rolling John, and let us know if you need anything else.

Hey Alice and welcome to E-Learning Heroes :) 

Hopefully John is still subscribed here to pop in and help you out. You are certainly welcome to reach out to the user directly via the 'Contact Me' option on the user profile if you do not hear back soon.

Hi Alice and Leslie,

What I've had success with is renaming the story.html file to story.aspx. Most SharePoint sites are set to not allow the running of HTML files, for web security reasons. When you post an HTML file on SharePoint, the user is generally forced to download the file to view it. Instead, SharePoint allows you to use an ASPX file instead. The idea is that HTML files run scripts on the user's local system (opening it up to security risks) and ASPX files run scripts on the server side and pose less of a security risk.

So... the file that allows the Storyline course to run needs to have an ASPX file extension. 

If you published with HTML5 and Flash, there will be two other files: story_html5.html and story_flash.html. In this case, the story.html is designed to determine which format is best for your browser (html5 or flash) and then redirect to the correct secondary html file. 

Chances are your users' browsers (and mobile devices) are HTML5 compatible and that's probably the best format to use. Instead of messing with the redirect code in story.html and then renaming it to story.aspx, I just make a copy of story_html5.html and rename it to launch.aspx.

Then, when the whole set of files and folders are copied to SharePoint, have users run launch.aspx and things should work fine.

Remember that you need to copy all files and folders of your published output to SharePoint, in order for the course to run. Since SharePoint doesn't allow uploading of folders through its Upload Document button or with drag-and-drop, you need to use Windows Explorer (File Exporer) to do this.

There are two ways to do this: use the Sync feature in the document library that creates a local copy of the destination library, and then copy the whole published folder to that synced folder. Or, you can have SharePoint launch Windows Explorer and have it opened to the folder you can copy to.

One thing that I have noticed with this approach is that SharePoint likes to run in Internet Explorer. I've tried this with Chrome and it doesn't quite work.

1. Using Internet Explorer, open the document library in SharePoint that is your destination.
2. If needed, click the link in the lower left entitled 'Return to classic SharePoint'. See attached.
3. The user interface changes and shows tabs in the upper left for BROWSE, FILES, and LIBRARY. Click on LIBRARY.
4. On the LIBRARY ribbon, choose Open with Explorer in the Connect & Export functions. See attached.
5. This will open a Windows (File) Explorer window directly to the SharePoint document library.
6. In Windows Explorer, navigate to the published output folder for your course. This may be under My Articulate Projects.
7. Click on the folder and press Ctrl+C to copy the entire folder.
8. Use the Back button (<---) in Windows Explorer to go back to the destination folder on SharePoint.
9. Press Ctrl+V to copy the published output folder to the destination folder on SharePoint.
10. Once the folder is copied, click on the folder to open it and locate the launch.aspx file. The .aspx file extension will be hidden, there should only be on launch file listed.
11. Click the elipsis button (...) to the right of launch.aspx and the URL of the file should be listed in a box. 
12. Copy the entire URL by selecting it and pressing Ctrl+C.
13. Now you have the URL of your course on SharePoint. You can paste that into an email or embed it as a link on a webpage, etc.

Hope my rambling makes sense. I may have to write this up in an article/job aid for the community, eh?

Let me know how it goes!

John