Can't edit trigger conditions on Input box. Help.

Jan 16, 2020

I'm trying to edit a Storyline 360 file created 2 months ago. I need to update trigger conditions, and the Storyline trigger options appear to have been changed since I created the module. Is this a bug? Did storyline update or limit my ability to edit trigger conditions? (and if so, can I roll back?). I'm stuck because the module has finally been approved by client, aside from a couple tweaks, but I can't reach my finish line here. Help needed.

My objective: I want to change the text input box variable trigger so that the variable adjusts when user begins to type. Currently it’s set for when input box "loses focus".

Problem: When I open the specific tigger’s editing wizard/dialog, there are no conditions at all, even though you can see in tigger summary (upper right) that there are conditions set. See screenshots #1 & 2.

Things I've tried: As a workaround, I tried creating a brand new trigger (to start over). In the resulting dialog box, I can now add/edit conditions, however now I have new problem in that the option the type of trigger to "when user begins to type" is no longer offered. See screen shot #3.

I've also tried rolling back my storyline options to use the old/classic trigger wizard UI, from the newer one recently released. That didn’t fix things.

Can anybody help? Thank you.
Lisa

System: Storyline 360, Windows 7 (Parallels VM), Mac OS Sierra

 

3 Replies
Katie Riggio

Hi there, Lisa!

Thank you for those screenshots and for walking us through what's happening. I haven't come across this behavior with the conditions in both the new and classic trigger workflows, so I'm glad you reached out!

Does this happen in a new Storyline course? Would you also mind sharing the affected .story file so I can try to replicate the problem? You can share it publicly here, or send it to me privately by using this upload link. I'll delete it when we solve this puzzle!

Fred Wehling

Hi Katie, 

Thanks for the reply. I'll upload the files directly after my response here. 

It looks like it doesn't matter if I work with a new file or if I change the SL preferences to use the old or new trigger workflow. 

I think this might be a resolved issue here as a non-issue, with follow up questions.

Q: If you're placing a trigger on a text input box, is there any way to make it so the TextInput variable auto-updates "as user types" (instead of when "loses focus")?  i.e., can this only be achieved with workarounds as discussed here? (https://community.articulate.com/discussions/articulate-storyline/set-text-entry-equal-to-typed-value-as-value-is-typed)

On the issue of "bug or no bug"... I don't think this was a bug, but rather my misunderstanding and expectations on how modifying triggers works for text input boxes. It may also be that this input type is more restricted (and not as consistent) as with other input controls. e.g., I expected the When condition to be editable and it doesn't appear to be. Seems you can only have on Loses focus. Or am I missing something? 

Uploading files....

Thanks. 

Lauren Connelly

Hi Lisa!

It doesn't look like the files came through, but I'll help out where I can!

There isn't a way to reword triggers but you can use variables in addition to triggers to create something similar to what you're looking to build. For example, you could add a trigger that says "Change State of Next button to Normal when the User Clicks Text Entry" with a condition " if Text Entry is not equal to blank". Here's what that looks like.

This discussion is closed. You can start a new discussion or contact Articulate Support.