Viewing Articulate 360 Content in SharePoint Online
Enabling Custom Scripts in SharePoint Online Custom scripts are now disabled in SharePoint Online for security reasons by default. As a result, Articulate content with the story.html file renamed to story.aspx in the published output that previously worked with SharePoint Online might not work anymore. If you don't need to track learners' progress or results, check out these free or low-cost options for web hosting. If you need to use SharePoint Online, your SharePoint admin may be able to resolve this issue by following the steps below, depending on whether or not you need access immediately. (Note that we don't provide support for either workaround.) Enabling Custom Script via the SharePoint Admin Center If you don't need instant access, follow these steps. Go to the SharePoint admin center and sign in with your credentials. In the sidebar to the left of the page, click Settings. (If you're using the Modern admin center, click the classic settings page hyperlink at the bottom of the Settings page.) Scroll to the Custom Script section, then select the options to Allow users to run custom script on personal sites and Allow users to run custom script on self-service created sites. Click OK to save your changes. Note that this change may take up to 24 hours to appear. Enabling Custom Script in SharePoint Online via PowerShell For instant access, follow these steps. Open Windows PowerShell with admin privileges, then run Install-Module -Name PnP.PowerShell Run this command: Connect-PnPOnline -Url <url> -PnPManagementShell (replace <url> with your SharePoint URL, which will then generate a code for you to insert in your SharePoint admin center.) Run these commands in PowerShell: (replace the URL after -Url in the first command with the link to your static site collection, such as https://companyabc.sharepoint.com/sites/StaticSite). (If you need help creating a SharePoint site, refer to this article from Microsoft.) Connect-PnPOnline -Url https://yourorg.sharepoint.com/sites/StaticSite $site = Get-PnPSite Set-PnPSite -Identity $site.URL -NoScriptSite $false Your SharePoint site is almost ready to host HTML files! We just need to prepare the Articulate published output for upload. Here's how. In SharePoint, choose where you will locate this project. You can create a new folder or use the Documents location created by default with all SharePoint sites. Rename all the files with an .html extension in your unzipped published output folder to .aspx (keep the same file name). To do this, right-click the file and choose Rename and then replace .html with .aspx. (Most projects only need to have both the analytics-frame.html and story.html files renamed.) Upload the published output to your SharePoint site, then click story.aspx to launch your Articulate course. This change should take effect immediately.505Views0likes62Comments.ASPX Files Now Download Instead of Launching from SharePoint
Hello all, My organization has recently discovered an issue with .aspx files hosted on SharePoint. We've been using them to launch Storyline and Rise files so they act like web pages (like this). However, we just recently found that after reuploading the file or folder to SharePoint, SharePoint no longer opens the page. If you navigate to the .aspx file, it force-downloads the file. If you use the direct URL, you get a File Not Found error. We suspect this is a SharePoint issue that has to do with the upload process. My IT department has asked me to check here to see if anyone else has experienced this problem, and if so, what the root cause was (e.g., Microsoft update, policy change, etc.)? We're looking at SharePoint because: It happens to multiple people in multiple offices (not a computer issue). It happens with Chrome and Edge. Modifying the URL to add ?web=1 has no effect. Clearing cache and cookies has no effect (not a browser issue). I tested the "old" file to confirm it worked, then downloaded the .zip package from SP. When I reuploaded the exact same package back to SP, the file now force-downloads/is not found (so it's not the files or the Storyline version). I copied a file that's still working and uploaded the copy. The original opens as a web page, the copy doesn't (again, not the files). Thanks in advance for your feedback!499Views0likes36CommentsAudio issues
Hello, The latest Storyline update appears to have caused a new issue with audio. I'm finding that when I have multiple audio files on a slide, and I use the seek bar, all the audio plays at the same time in an ear-splitting, hellish cacophony. A fix for this would be greatly appreciated. Thanks, SteveSolved330Views4likes16CommentsClosed captions not appearing
Not sure what happened with the last update, but now closed captions are not appearing on my video. The project is a single slide, video dropped in and the srt file uploaded. when i look at the captions editor all the captions are there, when I preview the file, the first caption appears then nothing after that. This issue started today after the update, didn't have the issue earlier today when i did the exact same process. anyone else seeing this?Solved230Views6likes23CommentsBuild an Accessible Drag and Drop Interaction in Storyline
If you've ever needed to build an accessible course in Storyline, you may know that the built in drag and drop interactions are not accessible (see the VPAT). However, with some extra work it is possible to create your own drag and drop interaction in Storyline that is fully accessible. The issue with drag and drop interactions and accessibility is that people who access the computer using only a keyboard or assistive input device, and no mouse, cannot click-and-drag. So, the interaction must have another option, that works through the use of keyboard inputs (typically, the tab and enter keys). In Storyline triggers, anything that is done "on click" can be mimicked by a keyboard or other input device. To build a keyboard-accessible drag and drop requires building a second set of triggers that function using click-based rather than drag-based interactions. Here is how to build your own keyboard accessible drag and drop interaction in Storyline. Please note that you may include other elements that are not fully accessible. Take a look at theWCAG Guidelines to evaluate other aspects of your course creation This interaction relies on a user-selected submit button. This button needs to be on the slide, as the triggers used are not compatible with the built-in submit button in the Storyline player. Note: It will be easiest to create all layers, elements, and states before creating the triggers. LAYERS NEEDED Base Layer – Most of the triggers will be on the base layer. Correct – A feedback layer for when the user submits the interaction, when all items have been moved to the correct drop location. Incorrect – A feedback layer for when the user submits the interaction, when the interaction is incomplete or some items have been moved to the wrong location on the screen. BASE LAYER Elements Needed Drag items – one or more Drop targets – one or more Submit button – one Drag Item States Normal - The built in state. This does not need to be modified. Selected - Create a “Selected” state. Make sure to edit the selected state to include a visual indicator that the item is selected. An easy way to do this is to add a “glow” shape effect in a color contrasting the object. Drop Correct - Create the “Drop Correct” state. You may want to visually signal that the drop was completed. One way to do this is to darken or desaturate the object in the “drop correct” state. Drop Incorrect - Create the “Drop Incorrect” state. Make this state visually identical to the Drop Correct state. Triggers Submit Button 1. Show layer Correct when user clicks If Drag item 1 state equals Drop correct And Drag item 2 state equals Drop correct … (Continue through the rest of the drag items) 2. Show layer Incorrect when user clicks If Drag item 1 state does not equal Drop correct Or Drag item 2 state does not equal Drop correct … (Continue through the rest of the drag items) Drag Items For each drag item: 1. Change the item’s state to Drop Correct when it is dropped on the right drop target Change state of Drag Item 1 to Drop Correct when user drops Drag Item 1 on Drop Target 1 2. “Deselect” all other drag items when this drag item is selected (Change other drag items’ states to Normal, if they are currently selected) Change state of Drag Item 2 to Normal when user clicks Drag Item 1 If Drag Item 2 state is equal to Selected Change state of Drag Item 3 to Normal when user clicks Drag Item 1 If Drag Item 3 state is equal to Selected … (add this trigger for all other drag items on screen) 3. Change the item’s state to Drop Incorrect when it is dropped the wrong drop target(s) Change state of Drag Item 1 to Drop Incorrect when user drops Drag Item 1 on either Drop Target 2 or Drop Target 3 … (include all incorrect drop targets in the list) Drop Targets For each drop target: 1. Move the selected Drag Item along a motion path to the Drop Target when the user selects the drop target. NOTE: The move triggers MUST be before the state change triggers in the list Move Drag Item 1 on Motion Path* when the user clicks Drop Target 1 If Drag Item 1 state is equal to Selected * For the motion path, create a line motion path with start and end points in the center of the drop target. This will move the object to the correct location without showing movement on screen. Make sure to go into the path options and select “locked” for origin. This will ensure that no matter where on the slide the object starts from, it will move to the correct position with the trigger. Name the motion path something descriptive so you can identify it in the trigger list (ex: Drag 1 to Drop 1 Path). NOTE: When you create a motion path, Storyline automatically adds a trigger to the object to follow the motion path when the slide timeline starts. Make sure to go in and remove all of these triggers. … Make this trigger for all drag items on the slide. 2. Change the state of the corresponding Drag Item to Drop Correct, if the Drag Item is selected Change State of Drag Item 1 to Drop Correct when the user clicks Drop Item 1 if Drag Item 1 state is equal to Selected 3. Change state of the selected drag item to Drop Incorrect for all drag items that do not match with this drop target Change State of Drag Item 2 to Drop Incorrect when the user clicks Drop Item 1 if Drag Item 2 state is equal to Selected … Make this trigger for all remaining drag objects on the slide. CORRECT LAYER Elements Text box(es) Continue button Triggers Continue button Jump to next slide INCORRECT LAYER Elements Text box(es) Try Again button Triggers Try Again button Jump to slide (current slide) – this restarts the interaction on the slide base layer NOTE: Make sure the slide is set to “Reset to initial state” for the “when revisiting” selection in the slide properties. And there you have it! It looks like a lot, but once you've done it a time or two you can get the hang of it. Below is an example .story file of this interaction. It uses the same names as the instructions above so you can see how this all looks in a project.199Views0likes94CommentsNew in Storyline 360: Integrated Review 360 Comments
When you need feedback on a course, Review 360 makes it easy to share your e-learning with stakeholders and collect their thoughts. It’s always been a handy timesaver—and integration with Storyline 360 will streamline your review processes even further! With the new Comments panel, you can browse through feedback, reply to and resolve comments, and quickly update your course with suggestions from your reviewers—all right from Storyline 360. By reducing the need to bounce back and forth between apps, you can speed up your revision process and trim down course production times. To access comments, first make sure you’ve published your course to Review 360. Then simply expand the Comments panel on the right side of your screen, just under the Triggers panel. To keep the process simple, this panel shows only the comments for the slide you’re viewing. And if you also use Rise 360, you’ll be happy to hear this feature is available there as well. Head over to the related discussion for more details: New in Rise 360: Integrated Review 360 Comments. If you’re an Articulate 360 subscriber, you can use this feature right now to speed up your course reviews. And if you don’t have Articulate 360 but want to see how much time integrated reviews can save you, you can start a free 30-day trial. We’re always looking for ideas for enhancing features. So once you’ve tried in-app comments, we’d love to hear what you think! Please share any feedback or suggestions in the comments below. The Storyline 360 TeamSolved199Views0likes93CommentsArticulate Storyline + JAWS + Slide Title + "F"
Our 508 reviewers have indicated that a slide title which is set up in a master slide, is reading the title followed by "F". For example, "This is the slide title - F." This does not happen in every instance of a slide using this master. It does not happen on other slide masters. Has anyone experienced a similar issue and, if so, what is the fix? Thank you!198Views0likes3CommentsTIP: Controlling the NEXT Button 101
It's great to let users explore content on their own. But sometimes you need to ensure they view the full timelines on the slides and complete the interactions. For example, this might be required for compliance/regulatory reasons. In other words, sometimes you need to control when the Next button is disabled and enabled. The attached file demonstrates how to control the Next button in these situations: Force users to view the full timelineon all slides by usingRestricted navigation Force users to complete an interaction byverifying that all of the buttonshave been clicked Force users to view the full timelines on the slide layers by verifying that all of the timelines have been completed The demo also explains how the triggers work. Nothing new here for advanced users. But I hope newbies find thishelpful. By the way, this is about controlling the Next button while the user remains on one slide. If the slide branches to other slides, well, that's a custom menu. You'll find details about those here: https://community.articulate.com/discussions/articulate-storyline/create-a-custom-menu-slide164Views1like20CommentsJump to Slide %Variable%
Surely there is a way to do this. I can create a trigger for each state of the variable. But this requires creating a trigger for each variable state on every slide that requires it. It would be much simpler to jump to a slide where the slide name or number is stored in a variable. Anyone know if this is possible? If not, why has articulate not added this seemingly basic feature? I found one reference to this but the link does not work. https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjRo9CJ5biIAxUnFTQIHUtqACAQrAIoA3oECCUQBA&url=https%3A%2F%2Fcommunity.articulate.com%2Fdiscussions%2Farticulate-storyline%2Fusing-variables-across-layers-to-control-slide-navigation&usg=AOvVaw2QUoGqGnutCZS6kf66SDFH&opi=89978449 Articulate responds that I don't have access, or it does not exist. Hmm.123Views0likes20Comments