Forum Discussion

LukeGleadall-d1's avatar
LukeGleadall-d1
Community Member
2 years ago

Simulator Text Field Error

Hi there,

We have recently made a series of software simulations and we have recently discovered an error. Within all of them we have opportunities for the user to enter text into a text entry field. If they enter any verbiage and press enter, then the simulation works and the user progresses to the next slide. However, if they mistakenly press Enter without entering any text then an error message comes onscreen with no way of closing the error box and going back to the Storyline file unless you refresh.

I've included the picture of the error box that one of our learners has experienced. I have replicated the same error in a different LMS, as a published file in Review 360, and as an offline file running my web browser only sometimes the same error box and its message pulls through the background image instead of black so the text is obscured.

Any ideas of how to solve this?

Thanks,

Luke

storyline 360
  • JoseTansengco's avatar
    JoseTansengco
    Staff
    2 years ago

    Hello Luke, 

    Thanks for reaching out! 

    I'd like to see how the feedback layers of your questions slides are configured. Would you be willing to share a copy of your project file here or privately through a support case? We'll delete it when we're done testing! 

  • LukeGleadall-d1's avatar
    LukeGleadall-d1
    Community Member
    2 years ago

    Hi Joe,

    As an update I have managed to find a workaround by adding the if condition after the "Jump to next slide; When Text Entry loses focus" trigger to state that "if TextEntry (insert number)  ≠ blank". That seems to bring up a regular message box of "Invalid Answer: You must complete the question before submitting" that can be closed when the user just presses enter.

    I also wanted to add that this error came from doing a Simulation through Storyline and not manually building it, in case that helps. Just wanted to close this loop in case it's a known or unknown bug at the moment.

    Thanks,
    Luke

Related Content