1. I see the issue with the Randomized test Actions. I didn't know that.2. If you go your JavaScript route, color me gone. I do very little.3. If you want to stay in Lectora, here is another alternate. Limit the user to say 5 questions they can mark. Use 5 variables to store the page addresses in when you are on the page and the user clicks a button to mark the page. (You might need 10 variables, 1 for the address and one for some sort of question identification like question number or name). Create one more variable for the number of questions marked.At the beginning of the test clear all variables.Then set up an ACTION GROUP at the test level and activate it when the "Mark this question" button is clicked.Action 1: Set variable 1 if number_of_questions_marked=0Action 2: Set variable 2 if number_of_questions_marked=1Action 3: Set variable 3 if number_of_questions_marked=2Action 4: Set variable 4 if number_of_questions_marked=3Action 5: Set variable 5 if number_of_questions_marked=4Action 6: Display: "Limit of number of questions to be marked has been reached" if number_of_questions_marked > 4Action 7: Add 1 to number_of_questions_markedOn the Results page, set up 5 buttons to go to these locations [GoTo - Web Address - var(variable) ]. If you want the buttons labeled other than "First question marked" etc, you are going to have to save question identifying info at the same time you save the URL and then update the buttons on the Results page. You can use updatable text blocks and make them look like buttons by setting the Borders property to "Raised bevel".
