This is a very complicated way to have a menu slide, you seem to ignore a lot. I suspect that Captivate is choking on that conditional action with so much Then/Else combinations.
I suspect that you toggle the variables with those loooooong names from 0 to 1 with the Back button of the last slide of that chapter? Why not add the 'Show checkmark' to that same action instead of always have Captivate checking the condition of that variable to show that checkmark? You can make an object visible on another slide without any problems. Moreover when an object is visible, it remains visible until you hide it again. The On Enter action should really only have the last decision 'AllSectionsDone'.
It is up to you to prefer show/hide instead of using states, unless of course you are on CP8 or earlier.
For the Back buttons use:
Assign v_section1 with 1 I used another name for the var, this is necessary for the On Enter condition
Jump to Menu
Show Check1
Personally I would use a shared action with the bold items as parameters, but advanced actions are OK as well.
There must be something else wrong, cannot see it, but wanted to offer you a much easier way to achieve your goal. All decisions are always executed, always in sequence. I try to avoid Else parts as much as possible when you have multiple decisions, except for the last decision. You can try to take out all the Else parts of the first, they are not at all necessary if you have hidden the checkmarks in output. But a clean On Enter action with only one decision will definitely be better. I would use multistate objects myself instead of show/hide but that is only possible for CP9 and 2017.
I don't think Captivate is choking on the Conditional Action as shown in those screenshots. I've done On Slide Enter CAs much more complex than that and they worked fine. If the menu buttons on this slide are not working, I suspect it's not caused by this Conditional Action. It's more likely to be the actions on the buttons themselves. I'd be more interested in looking at those next.
I recognise the variable names and syntax in this Conditional Action. It's one from a blog post on my website about Dynamic Menu Slides. It dates back to Cp7.
The initial Decision Blocks in this CA are just checking the tracking variables for each section visited by the user in the project to see whether or not that variable has been set to 1, indicating the module section has been completed and the check box against that item on the Menu Slide should be SHOWN, else HIDDEN. (Hiding objects that should not be shown, even if it's likely that they WOULD be still hidden anyway is just extra insurance that I have found to be good practice, especially in complex interactions. Has saved me a lot of debugging.) The Menu Slide in my blog post required the final decision checking all tracking variables because I had an extra caption and navigation button that appeared ONLY when all module content sections had been visited.
It might be personal preference, but I think it's better to have the Conditional Action that gets executed on entering the Menu Slide check each variable and then perform the relevant actions right then and there. Having an action on some other slide in the project show or hide objects back on the Menu Slide might still work, but doing it explicitly with an action on the slide where you want it all to happen will make debugging any display issues on that slide much simpler because the action responsible is right there in front of you, not buried somewhere else in the project.
This blog post was done back in the days before we had Object States in Captivate. That would definitely be another way to do menu slides, but either approach will work.
AdChoices