Agentry Language Reference

An application is represented as a definition type within the Agentry application project. Each project can have only one application definition.

The module level of an Agentry application project includes definitions for both data and user interface encapsulation. The data-focused definition types include business entity encapsulation, data capture, and data synchronization between the Agentry Client and Agentry Server.

The module level of an Agentry application project includes definitions for both data and user interface encapsulation. The user interface focused definitions encapsulate the screens and behaviors that expose the application functionality to the mobile users on the Agentry Client, but do not have direct impact on the behavior or functionality of the application as it is defined for the Agentry Server.

Rule function are the heart of most application rule definitions. Occasionally, a rule may be defined to contain a single rule term that returns the value of a global or other such data definition type; however, most rules are more complex and consist of multiple function calls.

To synchronize data between the mobile application and the back-end system, the back end must have access to the mobile application’s data values. This access is provided in Agentry using the Agentry Data Markup Language, or SDML.

The Agentry test script is an XML schema, supported by the standalone Agentry test environment, that you can use to automate testing the client behavior of a mobile application built on Agentry. The Agentry test environment includes a script recorder that lets you record, then play back, test scripts.

The Agentry Java API (AJAPI) is for Agentry applications that make use of a Java system connection for data synchronization. This API exposes the mobile application data to the Java logic, system and user information, and other key data needed during synchronization.