Forum Discussion
Quiz slides keep disconnecting from project
I am creating a graded quiz made of freeform (drag and drop) and graded questions. When I customize the feedback layer (add a 'Review' layer and delete the correct/incorrect feedback layers), the slides break apart from my storyline project and become stand-alone/independent in the storyview. My freeform questions are checked alongside the graded questions in the results. I am not sure what else to do.
The slides probably become stand-alones because the Correct/Incorrect feedback layers are where the Continue button usually is. Those buttons have a trigger to jump to the next slide. If there's no "jump to" trigger, the slide is disconnected. So try adding a "jump to" trigger wherever it's appropriate based on your design.
From my understanding, when you label the layer ‘Review’ storyline then
takes over and recognizes that. I also did try adding those triggers, but
then the whole quiz just “thinks” and never calculates on the results
slide.The built-in Review functionality automatically adds the Prev and Next buttons during a Review. However, those buttons/triggers are part of the special Review programming. Thus, by default, the Prev and Next buttons aren't available on a question slide. You can see this if you look at the Slide Properties; the checkboxes for those buttons aren't selected.
When those buttons are needed for custom programming on a question slide, just add them to the slide via the Slide Properties. Then use triggers to hide or show them when appropriate. For example, Next would probably be hidden when a question needs to be answered via the Submit button.
Another option is to turn off the Submit button completely. Instead, put that trigger on the Next button. That works wells when there's no immediate feedback (i.e., no Correct and Incorrect layers). Just be sure to put the submit-interaction trigger before the trigger that jumps to the next slide.
If none of that helps, I suggest you upload a copy of the .story file. It's much easier to troubleshoot that way, so someone might be able to figure out what's going wrong.
