We have an activity with storyline default Matching Drop Down template. We have a Submit button on it. Now the requirement is: The submit button should be initially disabled. It should get active once the user selects any of the options from the drop-down.
Why do you need to disable the submit button? Storyline has built in functionality, that will present the user with an error until the question is complete.
I have the same request from a client - we have a bespoke submit button on the screen (not one built in player) and the client wants it greyed out until they have selected all the dropdown items in the question - cannot figure out how to do this?
Hi, the storyline file is attached - what I am trying to achieve is the SUBMIT button to become active only once the learner has selected either at least one of the drop down answers or (what the client wants) to have selected all three.
I cannot see anyway of doing this as you cannot apply a trigger to a dropdown?
Lee, I know you weren't the original poster, but why (other than the client says they want it) do you need to disable the submit button? Storyline will prevent the question from being submitted and give a warning until the question is complete.
Hi Erin, yes I know, but in line with the general look and feel of the other questions and some knowledge check questions through out the module, the client would like this question type to act in the same way - ie greyed out button.
I've managed to do it on all other question types using trigger to change state if at least one of the check boxes are selected, but cannot apply that to a drop down question.
@Erin.. Yes, articulate prevent the question from being submitted by prompting the "Invalid Answer" popup. But this popup is not accessibility complaint, it has many issues
1. The content of the Invalid popup is read multiple times
2. Luminosity ratio of the "Ok" button is less than 4:5:1
3. Focus moves out from the 'Invalid Answer' popup without closing it.
4. The popup should get closed by pressing the 'Esc' key.
In order to get rid of these issues, we have to disable the Submit button.
Ok, so I worked out a solution myself which seems to work - apply a rectangle (with no fill or stroke) over each of the dropdown options. Next set a trigger to change the state of the rectangles to 'hidden' when mouse rolls over each one. Then create a trigger to change the state of the submit button from 'disabled' to 'active/normal' when the state of each of the rectangles = hidden. See attached storyline file as example.
It sounds like you needed some help getting the buttons in your Storyline 360 course set up properly. I'd be happy to assist with that!
Would you be willing to share a copy of your project file here in the discussion or privately through a support case? It would be helpful to take a closer look at what you've built out so far to see which settings need to be modified. We'll delete it from our system once troubleshooting is complete!
11 Replies
Why do you need to disable the submit button? Storyline has built in functionality, that will present the user with an error until the question is complete.
I have the same request from a client - we have a bespoke submit button on the screen (not one built in player) and the client wants it greyed out until they have selected all the dropdown items in the question - cannot figure out how to do this?
Attach your .story file (or a stripped down slide) here. If someone can take a look under the hood, they can suggest some options.
Hi, the storyline file is attached - what I am trying to achieve is the SUBMIT button to become active only once the learner has selected either at least one of the drop down answers or (what the client wants) to have selected all three.
I cannot see anyway of doing this as you cannot apply a trigger to a dropdown?
Thanks
Lee
Lee, I know you weren't the original poster, but why (other than the client says they want it) do you need to disable the submit button? Storyline will prevent the question from being submitted and give a warning until the question is complete.
Hi Erin, yes I know, but in line with the general look and feel of the other questions and some knowledge check questions through out the module, the client would like this question type to act in the same way - ie greyed out button.
I've managed to do it on all other question types using trigger to change state if at least one of the check boxes are selected, but cannot apply that to a drop down question.
@Erin.. Yes, articulate prevent the question from being submitted by prompting the "Invalid Answer" popup. But this popup is not accessibility complaint, it has many issues
1. The content of the Invalid popup is read multiple times
2. Luminosity ratio of the "Ok" button is less than 4:5:1
3. Focus moves out from the 'Invalid Answer' popup without closing it.
4. The popup should get closed by pressing the 'Esc' key.
In order to get rid of these issues, we have to disable the Submit button.
Thanks
Shraddha
Ok, so I worked out a solution myself which seems to work - apply a rectangle (with no fill or stroke) over each of the dropdown options. Next set a trigger to change the state of the rectangles to 'hidden' when mouse rolls over each one. Then create a trigger to change the state of the submit button from 'disabled' to 'active/normal' when the state of each of the rectangles = hidden. See attached storyline file as example.
Not perfect but this works for me!
I am facing the same issue.
For one of my projects, the requirement is the submit button should be initially disabled. It should get active once the user attempts all questions.
Please help.
Hi Prajakta!
It sounds like you needed some help getting the buttons in your Storyline 360 course set up properly. I'd be happy to assist with that!
Would you be willing to share a copy of your project file here in the discussion or privately through a support case? It would be helpful to take a closer look at what you've built out so far to see which settings need to be modified. We'll delete it from our system once troubleshooting is complete!
Looking forward to hearing from you!