The next tab in succession, Actions, is the actual "nuts & bolts" of the whole application. This is where the application begins, because the menus are all dependant on the actions.
We will go through the process of how to create an action, and you should get a sense of how simple the concept is. There are a few important notes about actions that are worth remembering.
Even thought it seems a bit preemptive, there are several things in the latter part of the application design that will be dependant on what you do here in the Actions area. Rather than revisiting this area later in the design, it will be better to understand the concept now.
First, as you create actions, menus, toolbars, and drop-down menus, you will notice that virtually all the items have an option to specify an icon property. All of these items also have the option to specify a particular action to associate with the menu, toolbar button, etc. Even if you assign a particular icon to these object properties, the icon of the action will supercede your selection IF you assign an action to the particular object. This is why it is important to build your actions carefully, and use the icons that you want to see in the end product at this level.
Also, as you will see later in the Toolbar design area, if you want to place a Drop-Down Menu Button on the toolbar, and only have the drop-down portion of the button (not the quick-select portion) active, to have an icon image show up on the button, you need to create an action, that has no real action, but that has an icon associated with it.
These are a few items to keep in mind as you explore the sample "Test Application" to familiarize yourself with the Application Designer.
If you expand Action1, by clicking the + sign on the left side, so that you can view its list of inherent actions, you see that there is only one action, ENTER USING Employee. If there were more, they would have been displayed in a typical "tree" format.
See Also: