Data Entry + Trigger

Hi Jessica,

I don't know if I thoroughly understand, but at least this will get you started and you can reply back to clarify.

If you're using the built-in next button, it will always display, but you can modify the trigger so it won't work until Learners have entered text in the text entry box, which is what it sounds like you have on your slide. The modified trigger would look like this:

ACTION: jump to slide

SLIDE: next slide

WHEN: user clicks

OBJECT: Next button

ON CONDITION: Text Entry ! = Not equal to (ignore case)

If you've created your own next button, you can set its initial state to hidden or disabled and have a trigger change its state to normal using the same condition.

Would that work for you?

Thank you for responding, 

Can you tell me what the differences are on the different types of conditions? Why pick the Text Entry ! = Not equal to (ignore case)? 

Also, how do I make my trigger changes state on my next button if I want all of my text entries to be typed into? I just make them all conditions like the one you told me and then once all of the text entries are typed in it will make my button appear? 

I really appreciate the info!

--Jessica

Hi Jessica,

So, for text entries where you want the Learner to enter some text before they move on, you want the text entry to be not equal to  blank (you don't want the text entry box to be blank). So, as you see in the screen shot below, your choices are not equal to or not equal to ignore case. If it doesn't matter whether the Learner types in uppercase or lowercase, you'd want to select ignore case.

Then, if you leave the value blank as in this screen shot, you're telling Storyline the Learner cannot move to the next page (or next "whatever) if the Text Entry field is blank.

And yes, if you have several text entries on your slide, you'll want to add the conditions for each to the next button trigger. It's always a good idea to name variables so you can keep track of what's going on, as in this example:

You may also want to add a Warning Layer to let your Learners know why, when they click Next, nothing is happening. If you're not sure how to do that, just holler.

The screen shots are fantastic! Just what I needed. 

I have one more question. Why can we not change the states for a data entry? For example, some of my data entry portions would be more valuable if I could add a hover feature for the user to see. Do you know why we cannot change the state? Or is there a way to get around this?  

Also, if I copy and past a data entry into another slide will that mess up the functionality? I believe I am just realizing this now! 

Thank you!

Hi Jessica,

Re: "Why can we not change the states for a data entry?"

I'm not as knowledgeable as many of the community members, but my "logical" answer (ask my husband if I'm logical ) would be that data entry text boxes are not "standard" shapes...they're shapes that contain..ummm...data, and so aren't handled by Storyline in the way that standard shapes are. I defer to others with more knowledge to confirm, refute, and/or explain further.

Re: "Is there a way to get around this?"

The only way I could imagine is to create a shape behind the data entry and give that shape a hover state. I've done that in the (bare bones) example I've uploaded BUT from a usability and Learner's expectation/design standpoint, I don't really like it. Because the hover state belongs to the rectangle, it disappears as soon as the Learner's pointer moves over the text entry. That's discomfiting. As a Learner, I'd wonder what I was doing wrong.

Someone else may have a better work around. I guess a good question to ask would be what purpose the hover state serves for your Learners.

If you look at the notes tab in this story you'll see what I did to create these boxes.

Re: "If  I copy and paste a data entry into another slide will that mess up the functionality?"

When you copy/paste a data entry, you are actually creating a new data entry variable. Take a look at slide 2, where I copied/pasted the First name variable. Then, click on the Manage Variables button, and note that there is a new variable named TextEntryF1

Is there a reason you'd need to copy/paste a data entry box?

For the hovering feature, you could always put a trigger on the text entry that whenever the mouse hovers over that, it changes the state of the rectangle (or whatever shape you choose) to "hover." This makes the hover action seamless and the glow will remain whether the mouse is over just the rectangle or if you're over the text box.

Great idea, Jesse! Slappin' myself upside the head.

Jessica, here's a screen shot for that trigger. Go, community!

Yay! The only thing I think you may want to change is the "When" area to "mouse hovered over." Of course, you could choose whatever action fits your situation.

Right - whatever Jessica has in mind. I was understanding from what I'd read that it was when the Learner clicks - but whatever meets her needs.

Rebecca, 

Little stumped here. I am doing exactly what you told me for the trigger and I still cannot get my button to pop up after all the text entry's have been typed in. Can you tell if I 'm doing something wrong from this screen shot?? 

So, from that picture this is what I am trying to do. I want the learner to type in all of those text entry and then the button to start the next step will appear. I don't know if I am using the And/Or function wrong or something different. Please help . 

Thank you! --Jes