Are Resources attachements, or links?

Thanks for the reply, Matthew.  So what you're essentially saying is that it creates a copy and attaches it (like an email attachment).  Great... 

Here's what I don't understand about this:  When the link doesn't work for my users, and I discover that the location of the file has changed since publication, wouldn't that imply that the link was broken because it was trying to pull from the old location?  In the case you've described above, the old information (attachment) would show up instead of trying to link to the new document.  No?

Hi Erin,

Did you include it as a hyperlink or web object to something on a server? Perhaps that's where the link issue is happening - as then if it was moved, Storyline can't reference to the old/original location? 

Also are you seeing this yourself? Where are you hosting your published content? Could the links to these files be blocked by the web server or LMS in which you're hosting? 

@Ashley:  

The Resource is a document (PDF, Word, or Excel) that is saved (or mapped) to our company drive.  For example:

 Company(K:)/Staff/Process_Documents/Admin_Assistant/Phone_Etiquette.pdf 

When I changed the file name to Phone_Skills, the link to "Phone_Etiquette" should be broken.  But it's still bringing up the file called "Phone Etiquette" which no longer exists.  This tells me it's been attached to the course like a copy.  

We host our elearning to a web server (not an LMS). 

Thanks!

This could happen if you published the course, uploaded it, changed the file name without changing the links, and published and uploaded it again. If there was no change in the triggers, the publishing process would not find the file, but would not give you an error message. Then if it was republished without changing the names or locations, the external_files folder would not be replaced, and the "Phone_Etiquette" file would still be there and still be accessed by the trigger.

I would expect this to happen only while accessing the published content; in preview, it would not find the file. If you are still seeing the old file in preview, that means it is not pointing to the location you think, but is finding a different copy of the file than the one you renamed. In the trigger wizard, you can test the location of the file, which will bring up the location the trigger points to.

Hi Erin,

When you include a file, it should include a copy of the file as a part of your .story file (currently we've seen so me issues with this which we've reported to our QA team for review) but the other thought is if you're linking to a non local file that could be causing issues as we always recommend working with local project files, including any linked files as detailed here.