I need to support a quiz type where the learner provides answers multiple questions (up to 30) before submitting them all for evaluation and feedback. Answers to all questions are ranged integers (e.g., 0 - 2, 0 - 17). The system they are training for uses a single data entry form where all the questions are on one page and all answers are selected via drop-down. The built-in quiz structures would require up to 30 pages of enter/submit before the user will see their results. Has anyone else experienced/solved this problem?
Yeah, that's a challenge. I'm guessing you wish for each question to be graded individually, and right now, you can only have one "grade" per slide. While you can certainly create a multiple question drop down on a slide (the method is to use convert to freeform and then evaluate all the entries), it only results in one grade (either they got them all correct, or they didn't).
If you're interested in the first half, here are two links:
Thanks for pointing me in the right direction, it saved me hours of dead-end exploration. I need the answer for each question to be sent to the LMS (as SCORM interactions) as well as the final result. With your help, I solved my challenge in a way that might be useful to others.
First, I created an HTML page that contained all my questions (30 for this particular test) in one HTML table. I then created 30 question pages in Storyline. Using the question names created in Storyline (e.g., TextEntry28) I then wrote JavaScript in the HTML file to update the question values via player.SetVar() calls and inserted it as a web object on the first page of the Storyline scene. Finally, I set the triggers for each of the question pages to 1) submit the interaction and 2) jump to the next slide (both "when the timeline starts").
Operationally, what happens is: 1) The web object is displayed within the player. 2) The user completes data entry via HTML drop-downs and selects "Submit Scores". 3) The embedded JavaScript then updates the Storyline questions with the values selected by the user. (None of the individual question pages are displayed to the user because of the triggers.) 4) The user sees the results slide, including the custom test-level feedback text created in the JavaScript code.
2 Replies
Keith,
Yeah, that's a challenge. I'm guessing you wish for each question to be graded individually, and right now, you can only have one "grade" per slide. While you can certainly create a multiple question drop down on a slide (the method is to use convert to freeform and then evaluate all the entries), it only results in one grade (either they got them all correct, or they didn't).
If you're interested in the first half, here are two links:
https://player.vimeo.com/video/145578775
http://vimeo.com/52342544
Hope this helps.
Mike
Mike,
Thanks for pointing me in the right direction, it saved me hours of dead-end exploration. I need the answer for each question to be sent to the LMS (as SCORM interactions) as well as the final result. With your help, I solved my challenge in a way that might be useful to others.
First, I created an HTML page that contained all my questions (30 for this particular test) in one HTML table. I then created 30 question pages in Storyline. Using the question names created in Storyline (e.g., TextEntry28) I then wrote JavaScript in the HTML file to update the question values via player.SetVar() calls and inserted it as a web object on the first page of the Storyline scene. Finally, I set the triggers for each of the question pages to 1) submit the interaction and 2) jump to the next slide (both "when the timeline starts").
Operationally, what happens is: 1) The web object is displayed within the player. 2) The user completes data entry via HTML drop-downs and selects "Submit Scores". 3) The embedded JavaScript then updates the Storyline questions with the values selected by the user. (None of the individual question pages are displayed to the user because of the triggers.) 4) The user sees the results slide, including the custom test-level feedback text created in the JavaScript code.
Thanks again,
Keith
This discussion is closed. You can start a new discussion or contact Articulate Support.