Application-Level Definitions Overview
An application is represented as a definition type within the Agentry application project. Each project can have only one application definition.
Within the application project structure, the application-level definitions are at the top of the hierarchy, and affect the application as a whole. The child definitions affect communications behavior, and provide global constant values that are used for configuration and other purposes. The definitions also include data storage on the client, in the form of tables and records that are accessible to the entire application, and definitions that affect the user interface appearance. The child definitions are referred to as the application-level definitions. Regardless of functionality, most of the application-level definitions are used in a given application.
The structure of application-level definitions within an application project is shown below. The
figure includes all child definitions, with the exception of the module. Modules are a
robust definition type that are discussed in a separate topic.
The child definitions to data tables and complex tables related to synchronization are dependent on the type of system connection. Synchronization logic is encapsulated in the language or methodology that matches the back-end system type.
The system connections of type HTTP-XML include child definitions that are related to user validation. The user validation request is sent according to these definitions, including arguments to that request. Responses from the request are mapped to the mobile application data components.
In general, when you are working within the Agentry Editor to either develop or modify an application, the application-level definitions dictate and control overall aspects of the application behavior, rather than within a given module or lower-level of granularity.