Update deleting triggers?

Hi all,

I know there are a number of issues with the Storyline update... got an issue of my own now. A colleague of mine, who is using the updated version, opened content which was initially developed with the non-updated version of Storyline. I then opened the content using the non-updated Storyline and all the triggers are now unassigned.

I'd simply like a confirmation that this was caused by using two version of Storyline and would like to know if there's an easier fix than having to reassign all the triggers.

Thanks

3 Replies
Adrian Dean

Hi Isa,

Not an easy way to fix it other than the one you mentioned. If you wouldn't mind submitting a support case however, we'll take a look at the issue that caused all the triggers to become unassigned. Make sure to include the .story file. Also if you wouldn't mind creating a screencast of the issue as well and including the link with the case submission as well.

Always Happy to Help,

Adrian

Ashley Terwilliger

Hi Kelly,

This thread is from 2012, so I'm not sure it's the same as the issue you're experiencing as we're also now on update 5 of Storyline.  Do you know what update you're using? You can go to the Help tab and click on About Articulate Storyline - you'll see a pop up window where you're Storyline update number will be listed. 

Now with that being said, there are a few other items I'd want to check. Are you and your coworkers sharing the same file back and forth seeing this behavior? If so, you'll want to follow the collaborative workflow outlined here, as working off a network or  USB drive could cause odd behavior in your files. 

If you're still having difficulty after working off a local drive and the behavior persists on a new file, you may also want to conduct the repair of Storyline to resolve any lingering issues.