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. (Note that we don't provide support for either workaround.) As of July 10, 2024, SharePoint users will find that they are required to reenable the Custom Scripts feature every 24 hours, reverting the Custom Scripts setting to its default and disabled state. Please see Microsoft’s article on Custom Script settings for more information. 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 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 a .html extension in your unzipped published output folder to .aspx (keep the same file name). To do this, right-click the file, choose Rename, and then replace .html with .aspx. (Most projects only need to rename the analytics-frame.html and story.html files. Finally, upload the published output to your SharePoint site, then click story.aspx to launch your Articulate course. This change should take effect immediately.TIP: 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 timeline on all slides by using Restricted navigation Force users to complete an interaction by verifying that all of the buttons have 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 this helpful. 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: TIP: Create a Custom Menu Slide | Articulate - CommunityTIP: Create a Custom Menu Slide
Do you want to create your own Menu slide? Do you want to ensure that the user can't advance to your summary and/or quiz until they have visited all of the other scenes in your course? Well, you're not alone. This topic comes up quite a bit in the Forum. Here are the basic instructions for creating a custom menu slide: Create a T/F variable for each scene (topic, module, branch, or whatever you want to call it). Set the initial value be False to represent that the user hasn't yet completed the scene. On the last slide of each scene, create a trigger that adjusts the corresponding variable to True when the timeline starts or ends (depending on your preferred restrictions). Alternately, add the trigger to the Next button. But if you do that, be sure the trigger appears before the trigger that jumps to the next slide. On the custom Menu slide: Add a trigger to change the state of the Next button to Disabled when the timeline starts. Include conditions so this trigger executes if any of the variables =False. (Tip: Be sure to connect the conditions with "OR" instead of "AND.") Add a trigger to change the state of the Next button to Normal with the conditions that all the variables are True. (Tip: Be sure to connect the conditions with "AND" instead of "OR.") To ensure this trigger executes every time a user returns to the custom Menu slide, have that slide "Reset to initial state" when revisiting. Or, if there are animations on the timeline that you don't want to repeat on revisiting, do this: Put the trigger on a blank layer, and set the Layer Properties to "Reset to initial state." You'll also need a trigger on the base layer to show that blank layer when the timeline starts. By the way, you can use the same basic instructions even if you don't include a Next button on your custom Menu slide. To do this, disable and enable whatever button you have for advancing (for example, a Go to Quiz button) using the steps above that describe how to disable and enable the Next button. Variables and trigger conditions provide the real power in Storyline. If you're not familiar with them, I highly recommend that you check out Articulate's User Guides. *** UPDATE *** I attached a file that demonstrates and explains how this works. If you scroll down in the comments, Sarah Hodge's comment links to an example that shows how to make the user go through the scenes/sections in order. *** UPDATE *** Articulate added the "Else" option to triggers with conditions. So instead of two triggers controlling the NEXT button (one to disable and one to enable), you can use one trigger with an "Else" statement.TIP: Track Responses to Custom Questions or Surveys
Do you want to customize a course based on the results of a survey? Do you want to create questions that assign different point values to different responses? In other words, do you want to track responses? You can do that by adjusting the values of number variables based on which buttons are selected. Then add up those values, and use that "total score" to customize what happens next. The attached demo file shows you how. It includes two examples: how to track multiple single-response items (like a Likert scale) how to track multiple-response slides In addition to the demos, the file explains how the triggers work. I hope this is helpful for those who want to track custom surveys and/or create question slides that assign different values to each response (instead of just grading right or wrong).TIP: Build a Rise Course with a Pretest
There is a way to include a pretest in a Rise course! Rise doesn't have pretest functionality built in—at least, not yet. But it can be done using a few Storyline blocks, some button blocks, and navigation restrictions. This demo shows how to let a user skip the content if they pass. If they fail, they have to go through the content. Rise course with pretest Caveats: The program can't tell the LMS if the user passed the pretest or if they went through the content. And it can't tell the LMS the user's score. But it can tell the LMS that the user "completed" the course. *** UPDATE 2024-01-17 *** As per Ingrid Marcum's comments below, there's another caveat. If a user fails the pretest, exits the course before proceeding to the content, and then relaunches the course, the Storyline block will reset. In other words, the user would be able to retake the pretest. As Ingrid said, the Articulate staff "confirmed that the storyline blocks will always reset when revisiting the page in Rise." So, alas, this method isn't a solution if you're concerned about users doing that.Using AI Assistant in a Rise Course Template
Hi All, Has anyone established if you can use the AI Assistant as part of pre-developed course template. I can see that you can use it within lessons themselves, so what I'm looking for is a way whereby you can upload the source documents for a new development, which retains all the course template features i.e company logos, brand colours etc... From what I can see, I don't think that's an option. My impression when this feature was first made public knowledge was that we could upload source documents and the AI Assistant would take the information contained within those documents and turn them into lessons, for us as Developers to then refine further if required. As an example, I've just uploaded a PowerPoint, and all it did was provide a suggested course title and created a course outline based on that title. It was then down to me to create lessons within each of those sections and add content, with none of the information from the PowerPoint anywhere to be seen. Am I missing something?TIP: Multi-character Scenario block
Have you ever wanted to use more than one character in a Rise Scenario block? As Glinda the Good Witch would say, “You had the power all along!” The Rise Scenario block allows you to choose a character and background for each scene. It’s one of those features that’s often overlooked. See a demonstration here: https://360.articulate.com/review/content/ca7a5893-9f69-4daf-a271-ead942b0b553/review The demo in Review also includes some basic instructions. The best to way learn? Try it yourself! If you’re unsure how to proceed, duplicate your scenario block, so you’ll be able to go back to an earlier version if needed. Note: I created the demo after seeing multiple questions in the Forum about using more than one character in Scenarios. But I think Storyline might provide a better experience, since that program gives you more control than Rise. The "best" option truly depends on the scenario/situation you want to show.The Value of Variables
Variables provide the real power in Storyline. They can help you track selections, control interactions, perform calculations, and so much more. Simply put, a variable stores data, which is known as its value. The value stays the same until a trigger adjusts it. The value can be displayed and used anywhere in the course. Based on the type of data it holds, a variable belongs to one of three categories. True/False variable A True/False (T/F) variable is like one of those Open/Closed signs that hang in a storefront's window, because there are only two possible options. The value of a T/F variable can only be True or False. Text variable A Text variable is like a written note. Its value can contain any combination of keyboard characters. It is possible to enter a number into a Text variable. However, the program will see the value as typed characters, not as a number. Therefore, you can't do math operations on a number in a Text variable. Number variable A Number variable is like an entry in a calculator. Because the value can only be numeric, the program can perform math operations on it. Variables can also be divided as follows: Project variables are created within a given .story file. Many Project variables are created manually. However, when you insert a data-entry field (text entry or numeric entry), Storyline automatically creates the appropriate type of variable to hold the value entered in the field. Built-in variables are used for values that might apply to any course. For example, there are built-in variables to control accessibility features, to number slides, and to report quiz results. Tips for working with variables When you create a variable, Storyline gives it a generic name (such as “Variable1,” “TextEntry,” or “NumericEntry”). To make development and troubleshooting easier, give every variable a new, meaningful name. It can help to display a variable’s value in a text box during development. That allows you to check whether the variable changes when expected. If the user doesn’t need to see the value, simply move that text box off the slide, hide it, or delete it before publishing the course. A trigger can be set to run when a variable changes. However, that kind of trigger only works when the variable changes on the same slide as the trigger. It's worth the effort to learn about variables. These links lead to more info. Storyline 360: Working with Variables | Articulate - Community Info about Built-In Variables On-demand training: Getting Started with Variables On-demand training: Using True/False Variables On-demand training: Using Text Variables On-demand training: Using Number Variables
