Modify the Agentry Eclipse preferences, which affect Agentry Editor behavior, as well as the appearance and behavior of various views within the Agentry Perspective.

The primary development tool for an Agentry mobile application is the Agentry Editor. The Editor is provided as a plug-in component to the Eclipse development platform.

The Agentry Editor provides several features for creating, managing, and publishing the Agentry application project.

The Mobile Northwind sample application is provided. The development documentation frequently references the Mobile Northwind sample application to help demonstrate how Agentry applications work. Following is an overview of this application, which describes the data structure, client behavior, and synchronization components.

Target paths are important to understand when creating or working with an application project using the Agentry Editor. Target paths are selected using either a short list of likely options from a context menu for a given attribute field, or by using the Property Browser for more sophisticated paths.

The Rule definition type is a module-level definition within the application project.

Rule definitions within an Agentry application project are added to the module, and defined using the Rule Editor.

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 SDML is a markup language containing data tags and function tags.

In any application the data structures and the processes to synchronize the production data are the foundation of the functionality.

When developing mobile software solutions, one of the primary considerations is the most efficient way in which to synchronize production data.

When developing a mobile application, data filtering is an important consideration during all phases of the development life-cycle.

The object definition is the primary data definition for modules.

The client-side user interface definitions architecture enables Agentry to support multiple client device platforms from a single application.

When developing the user interface for an Agentry mobile application, the first consideration should be given to the screen flow, which is how the user navigates through the information presented in the screens.

Use Agentry Editor preview mode during development to see how a screen will look on a device. You can also do some editing and positioning of objects in preview mode.

When developing a mobile application, security is always an important aspect to the process.

Within Agentry, you can attach documents, and perform some level of file management.