How about add Update Program Setting in that Change Menu Automation command to save automation command name? Then when yoy want to switch back just execute last save automation command name.
Yes I could create another 5 menus to replace the submenus. But then if I want to add subcategories to other menus the list of menus gets longer and automation for switching gets messier.
I just thought having the ability to navigate directly to a category or submenu would make it more flexible.
I guess this is not really a question i’m asking, its more of a request. I just thought there may be more hidden tags like the {:CURRENTMENU} that I just haven’t come accross yet
That entire flow seems counter productive. Surely we can come up with a better idea? Can you explain your menu better? Maybe we can suggest alternatives.
Well, I think I kinda get it that he want specific menu to be default at specific time. It can’t be done by using categories/submenu button because we have no automation for it.
Wait, I think you asked this question on the other post. I think the tutorial OP said he don’t have problem you having? I think might be something with constraint. It should execute only when ticket create, not every time anything change in ticket.
my menu is similar to this Switch Menus with FAST MENU
I’m using the menus as categories, so I can have a three tier category hierarchy vs the default two tier.
The tutorial OP is using entities so the ticket is created before any menu appears
I am using the create menu method with no entities so on ticket creation it navigates back to the department or ticket types default menu.
I have it set to only navigate on the ticket opened event so it does not happen every time an item is added.