Here is a sample, I created 4 different menus, for simplicity I called them A,B,C and D
And I created new Action called Generic Change Screen Menu
, I replaced two static fields with dynamic fields, which can be used in Rules dynamically.
I called them [:ScreenMenu]
and [:GroupFilter]
. I also created one more Action type Ask Question
. More about that in a sec.
Then I created an Automation Command or simply Button/Function. I called the function Menu Change Question
but for end-user purpose, I called it Menu Change. For end-user that are inputting orders on the daily and dealing with interface, less-is-more more often than not.
Then created 2 Rules. One that will handle press of the button end-user sees on the screen. And one that will manage second input of desired menu.
Change Menu Question Rule (will ask user to choose between one of those A,B,C,D menus I created via a bit of SQL magic) - Buttons get converted to [:CommandValue]
or value of the function if you want.
Question : Select Menu...
Buttons : {REPORT SQL DETAILS:SELECT Name FROM dbo.ScreenMenus WHERE Name != '{:CURRENTMENU}':F.Name::,},X
AMCName : Menu Change
Change Menu rule (will change based on input) - as you can see in the dynamic field we called [:ScreenMenu] we can pass a value called [:CommandValue] which is actually one of the buttons the user will press.
Final result:
Change Menu Dynamically MP4 + Import File.zip (480.7 KB)
P.S. You can use Database Tools in Settings > Database Tools > Tools > Import from File