Creating 2 menu levels with gating

Hi,

I've recently created a template for an eLearning product which will have 2 "levels" of gating. Essentially I have an main menu where you need to view 3 "popups" before you can move on to 5 submenu buttons. I've gated this initial menu properly and it works fine. The issue comes in on the second menu system where once you have viewed all items on the submenu the checked portion of the main menu doesn't work (even though it seems like the logic I have in place should work via variables). I have the sub menu show completed status (once all 4 items are shown as completed the "MenuCompleted" variable is set to true. Going back to the main menu after this doesn't show the items as completed (even though I have a slide trigger stating if "MenuCompleted" is true show completed state. Again it seems right but something is amiss... I just don't know if it's me or a bug with the logic/code/software.

It might be easier to send one of you the .story file (along with a more detailed message of specifically what I need changed) to see if you can help me figure out what's wrong. 

Thanks in advance. 

Regards,

Peter

6 Replies
Ashley Terwilliger-Pollard

Hi Peter,

Have you checked into the slides revisiting properties to ensure it's resuming the saved state and therefore saving your state changes to completed? If you're still having difficulty with it, as you mention, sharing the .story file or even a sample with the same behavior would be great so that we could take a look at how you've set up the variables and information. 

Peter Flynn

Hi Ashley,

Sorry for the delay on this response, some priority projects trumped this one putting it on the waiting list

I do have the file set up to resume the saved state but for some reason it's not working. How can I send the .story file to you directly (rather than on the forum)? 

Also, another thing we may do because this project is so large (and warrants multiple developers working on it in tandem) is creating a separate .story file for each lesson and having a main menu that you would go back to every time. Is this possible to do (connecting multiple storylines together)? Will this "checking off each menu button" still work if we do that?

Let me know when you can.


Regards,

Peter

Ashley Terwilliger-Pollard

Hi PF,

No worries - we're here when you need us.

I can send you directions on how to share the file with me privately. 

In regards to the section where you mentioned multiple developers working on the project in tandem, I do want to check that you're following this collaborative workflow for sharing the project file and working on it from a local drive instead of a shared or network drive which could cause odd or unusual behavior. 

If you haven't been working on it locally, I'd first like you to try importing the project into a new file and see if the behavior persists in that new iteration. If so, then can you also try recreating the behavior on a brand new project file that you work on from your local drive? If the new course continues to behave erratically, that's the one I'd like to see. 

If you're looking to work on multiple .story files, and then combine them at the end using that import process it would be a good way to divide up the work. If you're looking to link them once published, Storyline doesn't have a built in option for that - and it could cause some tracking/reporting issues depending on where you plan to host the published output and how you need to track the course. 

Peter Flynn

Hi Ashley, 

Thanks for your reply and help with this issue thus far. I appreciate the suggestions with this seemingly complex interface LOL. . I am (and have been) working on the file locally. I tried all the tricks you mentioned above and the behavior is still not working as intended. Perhaps I can send you the new file for you to take a look at? Let me know the best way to send this .story file to you.

Regards,

Peter