Text entry field - new error since last update
Apr 08, 2019
Hello,
We have many courses that require learners to input their names before beginning the module. There is a text entry field with the following code:
"Set LearnerName equal to the typed value When the control loses focus".
Then we have a "Confirm" button, with the following code:
"Change state of Error (a warning message) to Normal When the user clicks (Confirm) IF LearnerName is equal to (blank).
Change state of Next Button to Normal When the learner clicks (Confirm) if LearnerName is not equal to (blank)"
This has been working well for years. However, since I updated Storyline 3 to the latest release, the variable LearnerName does not register if I click Confirm (when published). I have to click somewhere else on the screen before clicking on Confirm (even if pressed multiple times).
I have attached a sample.
***EDIT: I can also confirm that courses published before updating Storyline 3 still work properly. Only courses published after updating present this error.
19 Replies
Hello Cyndy,
Thanks for reaching out and sharing what you are seeing in your project along with a sample .story for us to take a look at.
I noticed that you've published to CD. Is that the method that the content will be distributed to your learners with?
What browser/environment are you running into this issue? I was able to recreate the behavior, but only when viewing the output in IE11. Is this what you are experiencing as well?
Hi Leslie,
Thanks for looking into this. We have 2 methods of deployment: LMS on IE11 with HTML 5 (we are publishing with Flash backup right now as we transition away from flash) and CD version for our learners who need to download and view offline.
We don't upload to the LMS until the updates to the modules have been approved and they are still in testing, partially due to this error.
I tested on the SCORM cloud and it works properly in Chrome but not IE11, which is what we need to work, along with the CD .
Thanks for those details Cyndy. I was able to track down when this behavior changed and get it reported to our team as a software bug.
I wanted to share some information on how we define bugs and how we tackle them when they occur.
This conversation is attached so we can update you here when we can.
Thank you. In the meantime, can you provide me with a link to the last
version of storyline 3 before this problem occurred so that I can reinstall
it? This problem affects all of our learning.
Cyndy
Hi Cyndy,
That is a task our support team can assist with.
I see that you shared this issue with our support team as well, so I've updated Peter on our testing here and requested that he provide you the information needed.
I think I am having the same issue. I have a set of five text entry boxes where the variable is equal to the typed value. I also have some calculation triggers that run when the user clicks "Update". All of the variables are updating except the last one. All variables were updating when the calculation triggers were based on the "Next" button. However, my users want to be able to come back to the screen and see what they entered. In order for it not to redo the calculation triggers, I moved all the triggers to an "Update" button. If I tab or click anywhere on the screen before I click "Update" the variable updates. If I go directly from the last text entry box to "Update" the last variable doesn't set.
Hi Herminia
hard to say without seeing your setup - can you share the slide and we can take a look and see what's happening.
Here's my four slides. Click "Update" on the first slide. The second slide is the one with the issue. The last number entered will not update the variable, unless I "tab" or click somewhere outside the entry box. Here is an example of the numbers I entered: 6000, 8000, 5000, 4000, 1200, 600. Do not "tab" after the last number. Click "Update". Close the pop up box on the third slide. Notice that it does not report any numbers in the "Leave" row. It should read 600 minutes in the second column and 10 hours in the third column.
Hi Herminia,
Thanks for sharing some instructions as well as your .story file so that we can take a look.
I am looking at the third row on the third slide where it states 'Leave', correct?
When entering values in all fields and clicking Update, the value is set as expected. Here's what I'm seeing:
It works for me too in preview but not when I publish
Hi Herminia,
I spoke with the team at articulate and they have confirmed this is a software glitch that needs to be fixed. I was able to get access to an earlier version of storyline and that fixed my issue - you might want to request the same.
Got it, Herminia.
I am seeing an issue specific to viewing the published output in IE11.
Is that what you are experiencing as well?
Here is my published output.
Yes
Thanks for confirming, Herminia. This conversation is attached to the issue so that we can update you here.
Hi I have just started experiencing this issue, it previews fine but when published and playing in IE11 it doesn't pull through the person's name - Text Entry 2. I updated my version of SL3 relatively recently and it worked fine before. Could someone take a look for me please?
Thanks for reaching out and sharing your file, Amanda!
I tested this out in IE11, and I see the same behavior you described where the text entry value doesn't carry over. Things worked as expected in Chrome and Firefox for me.
From here, I've enlisted one of our support engineers to help troubleshoot and opened a support case on your behalf. One of my teammates will reach out shortly!
Thank you so much for helping with this. The engineer has provided a workaround of adding another button over my existing button. So the user has to enter their name, press enter (which changes the hidden start button to normal), then press start. Hope the bug gets fixed soon.
I appreciate the update, Amanda. I've linked this conversation to our report as well so that we can share updates with you here.
Hi, everyone.
I just wanted to share that we no longer see the bug reported where setting the variable when pressing the button is not working as it was previously using the latest build of Storyline (3.61.27106.0).
If you're using the latest version and you're still experiencing this issue, please reach out to our support team through a case.