Jump to next slide based on input from server, during runtime

Feb 10, 2017

Brandon McGruder
By Brandon McGruder

Hello all,

I'm trying to find a working scenario that does the following:

  1. A user would provide input (button selection) on a slide
  2. a variable value gets saved
  3. User presses a button that functions as a Next button (built in Next and Previous buttons disabled)
  4. JavaScript is executed to send the value to a server
  5. the server sends back a value to let my Story know what slide to jump to, from a selection of slides that are not linked by "Jump to slide...." triggers, and rely on this server input for slide changes.

I've made some mock slides to test it out, but the wall I'm hitting is that the Jump to Slide trigger forces you to select a specific slide while you're designing, and I don't see a way for the next slide to be chose during runtime as described above.

So far the only options I see are to add Jump to Triggers for every possible slide, on each slide, with variables to differentiate between them, but that's cumbersome?

Any better ideas? For example, can Articulate Storyline 2 slide transitions be performed in the Javascript itself? Or, does another Articulate program do a better job of this type of thing?

 

Thanks for your help.

5 Replies
Alyssa Gomez
7 years ago02/10/17 at 11:14 pm (UTC)

Hey Brandon!

Our team does not provide support for Javascript coding, but I do know that we have many savvy users that may be able to pop in and assist! By the way, did you mean to attach the mock slides here? That might be helpful in getting input from others in the community.

In the meantime, be sure to check out these Javascript best practices and examples.

Brandon McGruder
7 years ago02/14/17 at 4:03 pm (UTC)

@Michael

My understanding of the server side script is that it sends back a value that isn't random, but is based on algorithms being done on the server side, so we won't know what the value will be in advance.

The values sent back from the server are intended to let the Story know what screen to show next, and there's one question per screen.  So basically, the server side program chooses subsequent questions based on the input the user provides.

It doesn't have to play out exactly as I described above...if you know of ANY way to accomplish this two-way communication, I'd be interested to hear it.

 

Thanks.

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