Module-Level User Interface Definitions Overview
Within the module level of the application project in Agentry there are definitions for both data and user interface encapsulation. The user interface definitions encapsulate the screens and behaviors that expose the functionality within the application to the mobile users on the Agentry Client. These definitions do not have any direct impact on the behavior or functionality of the application as defined for the Agentry Server.
Of the user interface definitions, those that encompass the screens displayed on the Client are the most robust. The structure of these definition types is deeper than any of the other module-level definitions within the application.
Following is a graphic illustrating the module-level user interface definitions and their child and descendent definition types. This includes definitions that encapsulate the screens and screen controls displayed on the Agentry Client, the behaviors and functionality, and other similar user interface-related application components. Excluded from this graphic are the data definitions within the module. Note that this separation is for discussion purposes only. Within the application project structure, all child definitions to the module exist at the module level with no distinction made between them in the Agentry Editor in relation to whether they are data or user interface definitions.
The rule definition type within the module is actually one that crosses the line between a user interface and data definition. It is organized here with the user interface definition types, as a large portion of the rules written for a module affect this aspect of the behavior. However, rules can also be written and used within data definition types. The rule definition is described in this reference manual in its own section.
As indicated in this graphic, the screen set definition type is a deep structure, with several levels of child definitions below it. Note that, while separated in the above graphic, the list screen and detail screen items are both the same definition type, screen. A screen is a child definition to the screen set and, when defined, is either a list or detail screen. Each screen type has distinct child definitions, and thus are separated in the graphic shown here.
The field child definition to the detail screen can have child definitions of its own. This is dependent on the type of field defined, or the field’s “edit type.” The edit type of a field impacts the fields appearance and behavior on the Agentry Client. Certain field edit types include child definitions that support their intended behaviors. Field edit types are discussed individually within this section of the manual and those that include child definitions are noted.
Overall the user interface definitions within the module display, expose, and provide the means to capture data to and from the mobile users. User interface definitions can display not only data from the module, but also data stored in the application level definitions data table and complex table.