The Menus section is used to define menu bars that allows accessing different functions of the solution. Menu bars can also be displayed as Tabs which allow the user accessing different data sections quickly.
Menu items can be either of the following:
- A parent menu element, which contains child menu elements. Such menu item should not have a Flow nor a Page attached to it.
- A leaf menu item which triggers a Flow. In this case the menu item should have a Flow attached to it, but no Page.
- A leaf menu item which displays a Page. In this case the menu item should have a Page attached to it, but no Flow.
Menus and tabs
|Menu name||Name of the menu. This is the menu name shown to the user.|
|Flow||Trigger the given flow when the user clicks on this menu item.|
|Page||Display the given page when the user clicks on this menu item.|
|Read-only||If this option is checked, the DataSet attached to the Flow triggered by this menu will be in read-only mode.|
|Create new||If this option is checked, a new (blank) record will be created for the DataSet associated with the Flow triggered by this menu. This is equivalent of having a New action at the beginning of the flow.|
|Id (optional)||Id is used to group menus by logical meaning, and select which users can see which group of menus.
|Depth||Depth is used to define menus / sub-menus structure. You can have multiple menus with depth 0, in this case they will be separate (one of them can be used for the main system menu, another can be used to implement data capture tabs etc...).|
|Parameters||Some parameters can be set within a menu, and will be used when executing the associated flow or page. Syntax for parameters is param1=value1;param2=value2...
|CSS Class||CSS class applied to the menu item|