Can a trigger open the Resources tab

Hi there, Louisa!

You're correct - you can link to a single resource, but not the tab itself. However, there are some options that may work for you. Personally, I would recommend creating a lightbox slide instead and store your documents/links here. Then, you could simply open the lightbox slide from the "Resources" hyperlink you'd like to use in your slide(s). 

Another option, though it may be a little more time-consuming, would be to make a layer on your slide(s) that is designed similar to the Resources tab. You could even apply some transition effects if you'd like to get creative. 

In the meantime, if you'd like to see some additional functionality for the Resources tab, I recommend getting in touch with our development team. Personally, I'd love to see some additional player triggers - including the ability to call/close a specific tab. 

Thanks and best of luck! :)

Just finally got this to work, because

The example uses forward slashes /, but it should be backslashes \.

You have to turn on the Resources tab in the player. It's not enough to just upload the pdf as a resource. If you look at your publish folder and there is no external files folder, that's why, because unless you turn on the tab, the pdf doesn't publish.

EDIT: I realized later that I could just fake the same outcome by using the folder created when I published with the Resource tab showing. (Probably could have even made it from scratch). So, I turned off the Resource tab, then added the pdf to the publish folder manually. So, I created the file link in the trigger that reads story_content\external_files\myPdfFile.pdf, then placed a folder in story_content called external_files, and inside that is my pdf. Works like a charm and no need to show the tab.

My LMS team reports that it works as expected in SABA.

Hi. Thanks for this offer. I actually managed to get this to work - case sensitive was the problem, I found an e-Learning Heros post written by one of your team members that reminded about case sensitive. Loving the functionality - has made my job much easier to manage compliance standards, policies etc.

Thanks Christine! I'll submit it as a feature request.

Christine,

You make it seem like there's a way to link directly to a resource on the resource tab.  Is that correct?  For example, if I have a PDF listed in the Resources tab, can a button trigger that resource to open rather than pointing to a file location?

Thanks,

Michael

Hi Michael,

Absolutely - you'll want to follow these steps to link to a resource within your resource tab:

Here's how:

1. If you haven't already done so, add the file to the Resources tab in your player.
2. Then navigate to the slide where you want to link to the file attachment, and select the text or object that you want to be hyperlinked.
3. Go to the Insert tab, and click Hyperlink.
4. When the Trigger Wizard launches, select Jump to URL/File from the Action drop-down list.
5. In the File field, type the following text (but replace MyFile.xlsx with the name of your file, including the appropriate file extension): 
   
   story_content/external_files/MyFile.xlsx
6. Select the event that you want to execute this trigger from the When drop-down list, such as "User clicks". Here's an example of a completed trigger: 
7. Click OK.
8. Publish.

I don't see any benefit to following the steps above since adding a file to a slide that already appears in your Resource doesn't actually duplicate the file in any way. That's because when Storyline publishes the output, any duplicate files in the course with the same name are only contained once in the output. You can confirm this by testing the duplicate file process, then going to the published output folder location, look in /story content/external files. In fact, pointing to a file in the resources tab can cause more work since any future changes made to the file name or location of files in the resources tab, will require you to make updates to the triggers that are pointing to these files. If the necessary changes aren't made to those triggers, you're then left with a broken interaction. Unless you are keeping file names the same after each update, the process above does not lead to a reduction in file maintenance when changes are made to the Resource tab files.

Hello Pete, I would have to respectfully disagree, and would absolutely advocate Ashley's solution as a best practice.  

I believe that it is generally expected that when you need to update a resource like this the location and file naming needs to remain the same, or something is going to break.  Only needing to find and update that file in one location is a huge boost in efficiency for me!

Yes, I agree that not changing the file name is the ONLY way in which triggers to the Resources tab would work without causing more maintenance. However, what happens when you have version control protocols in place in which the file name needs to reflect updates made (e.g. file_v3.b or file_2014.doc). Then you are required to change both links in which case resource tab triggers are not efficient. And I've also had strange instances when keeping the file name the same for the purpose of reducing maintenance of links but was still led to the old file even when clearing my browser's cache. Other users have reported similar issues with documents not updating properly here. This isn't consistent but I've had this happen on more than one occasion and the only workaround for me was to rename the file. So for these reasons, I am motivated to change triggers on both ends. However, it basically comes down to what process you are using based on your project's requirements and whether your documents are updating properly each time.