@Mike, @David & @Jennifer,
In this case, what I am trying to do is give the user a list that they can take to the "powers-that-be" at their organization. These questions apply mostly to pilots who are part of a larger organization (such as airlines) and, although they may not be the owners or the ones in charge of policy-making, they can certainly help to make the organization better by giving these suggestions to their higher-ups, as the list will already be tailored by their individual feedback. It is because of this that giving the suggestions after each question does not really help as it is not necessarily the pilot who needs this list, but the ones who can put these policy changes in place in the organization.
I started setting things up as per Mike's suggestion and it seemed to be working great! Because each number of possible suggestions narrowed down which suggestions could possibly appear in each position within the list (ie - with 11 "No" answers, there will be 11 out of 11 suggestions appearing on the list and each suggestion can only appear in one spot. With 10 "No" answers, there will be 10 suggestions on the list out of 11 possible, so "Slot 1" could have either Suggestion1 or Suggestion2 appearing in it and "Slot 2" can only have Suggestion2 or Suggestion3 appearing in it, etc. With 9 "No" answers, there would be 9 out of 11 possible suggestions appearing on the list, meaning that "Slot1" could have Suggestion1, 2, or 3 in it, "Slot2" could have Suggestion2, 3, or 4 in it, etc.), I thought that would narrow down the number of triggers required to show each suggestion within the list. That part was true, however, it wasn't until I started getting into seeing how many triggers would be required to account for which questions the user didn't answer "No" to that it got staggering! Mike mentioned this fact and he is correct on both accounts - it does work - but it was just going to be too much to try and set it all up once I got into less than 8 suggestions appearing on the list! Mike's solution works very well if you have less options to be considered, though, so if anyone needs a similar setup with fewer options (I'd say 6 or less), download his example and mimic it, for sure!
I would like to minimize the number of additional slides that the user has to click through for feedback as they have already had to click through 11 question slides and then a report card slide in this single exercise alone, so, although David's suggestion is excellent and would work, I'd rather find a way to put all of the suggestions on one slide. After playing around with it some more, I have realized that it is going to take even more playing around, so I have moved on to other aspects of the project and will come back to this at the end. I've been thinking about this issue while going to sleep, in my dreams, when I wake up, while in the shower, while driving, etc! and I think that I have finally figured out a way to make it work. It is going to involve having a separate slide for each number of possible suggestions (I have already created a variable that tracks their total "No" answers that can be used with triggers to show the correct slide) with each slide having separate layers for every "Slot" in the list. Then, I can use variables to indicate whether or not each slot is already filled and have triggers on the layer to say which suggestion to show in that slot. Basically, it will be using part of what I was doing with Mike's suggestion but breaking it down onto more manageable pieces (I hope!). It is still going to be a lot of work to get it all set up but, in theory, it should work (although the same can be said of all of the other approaches I've tried!) I will upload my final, functional model if I can ever get it to that point! Do you guys offer a contest for the most complicated models that people can build with Storyline? Maybe you should! Lol!
Thank you very much for all of the assistance that you have all been offering - it's still helpful to help me figure out different ways of approaching this!