SCORM Tracking - html5 version remembering another template course

Hi, 

Can someone from Articulate reply to my original question please.

Trevor

Hi Trevor,

Sorry we missed this on Friday - so thanks for coming back around.

When conducting a "Save as" I wouldn't expect the random identifier to change, and I know of no risk to manually changing the identifier. 

I can't think of a special process you'd need to go through. You'll want to conduct your "save as", publish and ensure that file name is different than previous versions, upload to your LMS and then test it out. If it's not working in your LMS, you will want to test this as well in SCORM Cloud, as that's an industry standard for testing SCORM content. 

Also, you mentioned you're only seeing this in the HTML5 content - so you'll also want to confirm you're using one of the supported browser documented here for SL1 and here for SL2. 

Hi Ashley,

I'm still having major issues with html5 SCORM resume (no cookies) being remembered from an originally course after a 'Save As' project build.

So as described in my original text above I have new courses based on previous courses. Every piece of publish settings which identifies the original course has been changed in the new version. As I'm connecting to an LMS with SCORM, in the player I am ignoring cookies for resume settings. However when the new course is launched on an iPad it is still picking up tracking 'resume' data from the very original course (different ID) so I'm being returned to the wrong resume status. I have cleared the cache. I'm working in Storyline version 1.6 and 2. 

If I create a new course from scratch, launch and relaunch between PC, ipad, Android the resume data is behaving as it should i.e. giving me back the last true reported status.  

Is it possible to ask the Storyline developers if there is some other internal identification code within a Storyline course that mobile safari is saving which I haven't manually changed?  I don't want to be building every course from scratch to avoid this issue. Or maybe they know of some other reason why html5 resume is picking up information from another course with different course ID.

I really need to crack this.

Trevor

Has anyone from Articulate read my previous post added yesterday?

I have been doing some more testing and can't figure out what is causing this issue. I would like to send you a example course for you to test however I can't provide a link in the thread as it is client specific.

What support can you provide me?

Regards

Trevor

Hi Trevor!

Sorry that your post was missed. If you ever need to send private files, you can send them via this link.

Hi Trevor,

I'm glad Leslie was able to provide you the link, and my apologies for missing your post yesterday. Were you able to test this in SCORM Cloud as well to see if the same behavior occurred? If you saw the same thing in SCORM Cloud, please feel free to share information with us privately using that link above. 

Good morning Leslie and Ashley. I have this morning submitted a support case which contains both the published course and the source Story file. I have referred this post number in the support case.

I have tested on both Moodle and SCORM cloud and get the same html5 error.

I have been working through all the possible errors but have drawn a blank. I'm hoping Articulate can spot what is happening.

Regards

Trevor

Hi Trevor,

Thanks for letting us know and I see your support case (# 00429500 for our reference) and we'll continue to follow along as well to update anything here for others who may be watching this thread. 

Hi Ashley. Ok, the error was as the result of corrupt variables and/or triggers related to variables. By using 'Save As' and building new courses based on a corrupt file simply populated the same issue.

The solution to fix an affected course was:

1) In the original .story delete any triggers related to variables and then delete the variables.

2) Make a new story with the same dimensions and import all the slides from the cleaned up original.

3) Add new variables the same as the ones deleted in step 1 and then the same triggers.

When published the resume on the custom menu (driven by variables saved as suspend data) was working correctly in html5 and I can once again jump between flash and html5 with no loss of custom menu tracking.

I'm using this method to repair the four affected courses but I'll start with a refresh build for the next new course instead of using 'Save As'.

Going forward I would recommend the 'Import' if you have two course very similar to each other.

Trevor

Hi Trevor -

Another way to go about this is to try saving as a Story template. When you re-open a file.storytemplate file, it should initiate a new file with new identifiers.

Hi Steve,

Thanks, I'll have a look at templates once I have cleaned up the corrupt courses.

Cheers

Trevor

Thanks Trevor for sharing the update here and letting us know what you were able to do to fix it. 

Ok, back to square one again. I did successfully rebuild the first affected course. However I rebuilt a second course today using the same method, i.e. deleting triggers and variables then  importing cleaned slides into a fresh course file. Can't spot a major difference between the first and second rebuilds. They share the same variable solution to drive a custom menu. Again it is only the html5 version which is affected.  So it looks like I'm faced with complete rebuilds from scratch i.e. every object and layer on every slide.

Has anyone come across a known situation which has caused corruption to variables or triggers?

I have spotted one strange thing on a few slides in a course which failed where I can't paste a trigger onto a slide if in 'story view'. If I fully open the slide I can paste the trigger. I'm wondering if it is actually pasting the trigger the first time but it's not showing it and then I paste the same trigger again.

Any ideas or experiences welcome.

Trevor 

Hi Trevor,

I'm sorry to hear that this issue continues for you - but I did test the element you mentioned about copying triggers in story view, and that works as expected for me. I see the trigger appear immediately and it appears in succession where it should. I tried this on one slide and between slides. Once you've pasted the trigger in, I assume you scroll through the list and don't see it? Do you see it once you've opened up the actual slide and look at the trigger panel? 

I see that you and Regil went through a number of the repair steps, and that you're also working with Cleo now on an install issue - you may want to update Cleo on some of the other "oddness" you're experiencing with copying triggers and such. 

Hi, I agree the copying triggers in story view seems to be a specific bug in one file. In this case the course has about 50 slides and I need to apply a second trigger to the same button in all 50 slides. It's quicker to do this in story view as I have the trigger panel open on the right and can highlight the button required without opening each slide. Pasting works in 47 slides but in three slides pasting is not working. As I can see the whole of the trigger panel without scrolling (I have a very high res screen) I know the trigger hasn't been placed somewhere else. If I open the three slides concerned pasting then works.

I'm wondering if these three slides maybe the cause the corruption I'm seeing. So I'm going to delete these three slides from the cleaned version i.e. removed variables and variable related triggers and see if that fixes the issue in this particular course.

Trevor

Thanks for the additional info Trevor - and it may be something on those slides as well, so as you insert them back in you may want to look at reinserting the elements one at a time and trying the copy/paste between those attempts to see how it behaves and if you're able to isolate the element of corruption. 

If anyone comes across this thread regarding corruption of variables with html5. I'm pleased to say that Storyline 2 update 5 contained a fix for 'True/False variables always returning as True after resume on HTML5 version'. I have this morning tested my courses with custom menu which are driven by true/false variables and the problem is fixed. I am one happy person.

Thanks for sharing this update Trevor :) Happy Friday!