Triggers not working in SL2

Hi all,

We recently upgraded to SL1. While I LOVE the new version, we are experiencing issues with triggers that are no longer working with courses that have been upgraded to SL2.

Here are a few examples...

  • One course has next triggers based on a variable that prevents them from clicking Next until the very last text box or object on the slide appears. This worked perfectly in SL1 but the triggers no longer work in the SL2 version. I have tried deleting and re-adding the triggers but they still don't work.
  • Another course has a hotspot that advances the slide when they right-click. Again, it worked perfectly in SL1 but no longer works in SL2. I have added, re-added, no luck. I have also removed the hotspot and just added an empty box with a trigger to advance on right-click and that isn't working either.

Has anyone had a similar issue? Is there an issue with the process of the SL1 file upgrading to SL2? Do we need to recreate these courses from scratch in SL2 (I hope not!). Thanks!

24 Replies
Christie Pollick

Hi, Kari -- Sorry about the issues you are having after upgrading to SL2!

Would it be possible for your to share your original SL1 file so that we can attempt to upgrade it to SL2 (in order to see if we encounter the same behavior on our end)? And you're also welcome to share your SL2 file to illustrate the issues you have detailed above. 

Kevin Long

I'm having the same issue as your first example and came up with this work around.  I had to add a slide trigger that changed the state of the text box to Normal.  I then set the State for the text box to Hidden.  I then added a condition to the Player trigger that allowed the user to jump to the next slide when clicking the Next button on the condition the text box state was normal.  I Just posted up a question on the issue but looking for method other than my work around becuase I have 56 modules that we converted and will now have to use this work around if there isn't a better more efficient solution.

Thanks 

Kari Thevenot

Hi Christie,

Thank you for your reply. This particular attachment is an SL2 file that was created in SL2 from the start. Using an identical process to SL1, I modified the next button trigger on page 2 so that the Next button wouldn't be clickable until the last box appeared on the page. It works great using SL1 but not in SL2. 

Kari Thevenot

Here is that very same file but upgraded in SL2. As you can see, the variable no longer works on page 5. Previously, I had always removed the Next button whenever we needed a delay and inserted my own right on the page....but having the ability to use the variable on the existing Next button is ideal and makes things more clean. 

Christie Pollick

Hi, Kari - Thank you for your patience while I took a look at your files. I see the issue you mentioned about the variable that no longer works on page 5, and I would like our Support Engineers to investigate this issue more in depth for you. I went ahead and created a support ticket and submitted it on your behalf, so you will be hearing from someone on that team shortly via email. 

Jordyn Matusevich

Hi -

Was there any solution to this issue? I had this problem right when SL2 came out with a huge 10 module course and the Articulate support team never found a fix and just told me that they elevated the issue to the QA team. This just happened to me again with 5 courses that about 200 people take around the country per day (and is a prerequisite to hiring and beginning employment at my company). Needless to say it caused some huge problems and users could not advance through the courses. I ended up having to take all the triggers off the courses and users no longer have to complete all activities on a slide before advancing just to make sure they are able to complete the courses and begin working. 

Leslie McKerchie

Hi Jordyn!

This issue filed on this thread/case is still in the hands of our QA Team. The information from your case (00474619) leads to the impression that you were able to reach a workable resolution and that the issue was caused during upgrading of files. You are welcome to work with our support team if you need something re-evaluated or you are having a new issue.

Kevin Long

Hi Jordyn,

I’m not sure if it is exactly the same issue you may have experienced but I was able to resolve mine. While analyzing the issue, I found it to be a matter of simplifying the manner in which the triggers were set up which allowed me to even reduce the amount of triggers and objects. I determined the team previously involved had implemented a work around because they may not have completely researched or understood the appropriate steps needed and over complicated the process flow.

Jordyn Matusevich

Hi Leslie - 

Yes, the issue was caused by the upgrading of files from SL1 to SL2. I did not come to a resolution - unless we consider using the the backup SL1 file as the solution. There was no solution to fix all these triggers that no longer work properly. The new issue is the same issue as before - is there a fix or a reason that simply upgrading the file makes my course unusable as is? I supposed I'd have to open another ticket with support and go through the process again? :(

Ashley Terwilliger

Hi Jordyn,

Upgrading the file shouldn't make it unusable or cause triggers to no longer work - but it was likely something in the file or on the system that brought in an element of corruption.  It seems the issue that occurs is the triggers are validated incorrectly - so another user shared that they'd either use the Next button "Disabled" state or the variable True/False to help track this and not have to remove all the triggers. 

Kari Thevenot

Good morning,

I wanted to provide an update to the original issues that I posted a while back. Both my coworker (Bailey) and I got the version 7 update for SL2. Her issue with the right-click trigger has been resolved. However, I am still not able to put a trigger on the Next button that doesn't advance the slide until a certain part of the screen appears. 

I have tested it in both versions. I'm attaching two files to look at. One is an SL2 file that was created in SL2 (not an upgrade from SL1). The other is a sample I created in SL1. I have these set up to allow Next button advance when the last image appears. As you can see it works great in SL1 but doesn't work at all in SL2.

Jordyn Matusevich

Hi Ashley,

 

So we think it is corruption? This trigger invalidation has happened to every course I've upgraded to SL2 (quite a few). While I realize the triggers don't have to all be removed, the solution/fix still involves me manually changing all the triggers. This doesn't seem to be a very good solution to something that should work after buying the updated product.

I have hundreds of courses for an audience of over 65,000 and a design team of 2.  It proved faster and easier to remove the faulty triggers so the employees were able to pass the courses and begin working for us - but obviously that's not the ideal solution for the future. Since it's happened every time - I'm afraid to upgrade any more b/c clearly it will continue to occur.

Is there any way to avoid this without having to manually put different triggers in place?

Christie Pollick

Hi, Kari -- Thanks for the follow-up, and I will test both of your files as soon as possible and let you know what I experience. 

Hi, Jordyn -- Ashley is out of the office the remainder of this week, but I will do a bit more research on your query, and try to provide you with more information as quickly as I am able. 

Thank you both for your patience. :)

Christie Pollick

Hi, Kari -- I was able to experience the behavior your described in your SL2 course where the Next button did not behave the same way as it did in the SL1 example. I will create a new Support ticket on your behalf and send it to our Engineers for additional investigation. 

And Jordyn -- I am still in the process of gathering additional information, so your continued patience is appreciated. 

 

Kari Thevenot

Hi all,

I have an update to the Next button trigger. Articulate opened a new ticket for this and they are sending it on to Quality Assurance. In the meantime, the person assigned to the ticket offered a workaround, which is setting the variable to NOT equal Hidden instead of equal to Normal. I have tested this on my sample file in SL2 and it does work! I'm hoping maybe this can help others. 

Christie Pollick

Hi, Jordyn -- Thanks for bearing with us. Unfortunately, at this time, it looks like your issue is still being investigated by our QA team, so I do not have another workaround to suggest other than what you already mentioned (to manually put different triggers in place). Any updates or news we receive will be shared here in the thread as soon as possible.