2 Questions

I am refitting some modules and have discovered two anomalies:

1. Triggers that work in Storyline preview to show a layer when clicked outside a hotspot do not work in Saba; they instead show the second layer on a first click outside the hotspot in Saba. I have variables created that should show the second layer only after a trigger on the 1st layer changes the variable from True to False. I understand from previous conversations with you that variables should not be re-used within the same scene. That's not what's happening here. I'm re-using variables from two previous scenes.  I've set up triggers on my initial transition slide for the new scene to set all those variables to True if they're currently showing False. But, why is this happening? I have to ensure a consistent method for using these triggers and variables; we're developing over a hundred modules and working with 5 contract developers.

2. The links between a document attached as a resource (PDF file) seem to be breaking on these older modules after uploading to the LMS. They show an error message. An acceptable work-around is *not* to delete and re-attach every time. Why is this happening? How can we prevent this so we *don't* have to re-attach before each upload? We use zip files in SCORM 1.2, include HTML5 output. 

 

Thanks very much for your input!

Deb

1 Reply
Alyssa Gomez

Hi Deb!

Thanks for sharing your file here. I uploaded your file to SCORM Cloud,  which is an industry standard for LMS testing. Here is a link to your file in SCORM Cloud.

It seems that your layers are working as expected - the Try Again layer shows on the first click outside the hotspot, and the Incorrect layer shows on the second. Also, the PDF in the Resources tab appears normally. Please test the link on your end to ensure everything is working properly for you.

If your course works properly in SCORM Cloud but not in your LMS, I would recommend that you open a support case with your LMS provider to troubleshoot the issue. They’ll know how best to help with LMS-specific problems.