Developer

Module

The module definition is a group of definitions that provides functionality that logically belongs together. The module attributes and child definitions define the majority of the behavior and functionality exhibited on the Agentry Client at runtime.

Application modules contain the functionality that is related to the user interface on the Agentry Client, data storage and structures, data synchronization, and data capture. Any child definitions of a module also have access to all application-level definitions.

An application project must contain at least one module. When multiple modules are defined for an application, users are required to select which module to work with when logging in to the Agentry Client application. They can switch between modules using the Agentry Client View menu, which lists the defined display name for each module within the application.

The module’s child definitions are primarily intended to work with other definitions within the same module. You can define cross-module functionality using actions within one module that may execute actions of another module within the same application.

Module Child Definitions

  • Objects: An object definition encapsulates a business entity and its related data.
  • Screen Sets: The screen set is the main Client user interface definition and defines what definition type its child screens display.
  • Transactions: A transaction definition defines what data is captured on the Client, how that data affects a target object instance on the Client, and how the captured data is processed by the Agentry Server.
  • Actions: An action defines navigation and user interaction for the Agentry Client, bringing the other components of the Client’s UI together.
  • Rules: A rule defines evaluation logic processed on the Agentry Client that returns a single value to the caller of the rule.
  • Fetches: A fetch defines how SAP Mobile Platform Server synchronizes data for a target object collection by referencing the step definitions to perform this task.
  • Steps: A step defines a piece of processing to be performed by SAP Mobile Platform Server with a specific back-end system.
  • Reports: A report defines a printed tabular report format for the contents of an object collection on the Agentry Client.
  • Pushes: A push defines when it is necessary to push an object in real time from the back-end system to the Agentry Client and how that object’s data is retrieved.
  • Service Events: A service event defines how SAP Mobile Platform Server synchronizes data between two back-end systems, usually based on a change or “event” occurring in one of the systems.

Module Attributes

  • Name: The name of the module. This value must be unique among all modules defined within the application.
  • Display Name: The text that is shown to Agentry Client users at runtime. This value appears in the Agentry Client Module Selection Screen, and also in the View menu.
  • Preserve Objects: If this attribute is selected, the objects are preserved when a new user logs in to the Agentry Client on the same device as the previous user. If not selected, a user change results in the objects being removed before object data is synchronized for the new user.
  • Image: The image definition to associate with the module definition. This image then appears for the module in the Agentry Client Module Selection Screen.
  • Successful Login Action: The action to be executed within the module after a user successfully logs in to the application. The action executed here targets the module main object. For multi-module applications, where more than one module defines a Successful Login Action, the order in which those actions are executed is undefined.
  • Application Exit Action: The action to be executed within the module just prior to exiting the application. The action executed here targets the module main object. For multi-module application,s where more than one module defines an Application Exit Action, the order in which those actions are executed is undefined.
  • On User Change Action: The action to be executed within the module immediately after the Agentry Client detects that a user change is in progress for the original (or previous) user before the user changes takes place.

Module Styles Attributes

Screen Set Styles
  • Header: Header style when there are multiple screens within an object screen set. Different screen styles help Agentry Client users distinguish between the header area of a multiple screen set and the tabs for that screen.
Screen Styles
  • Tabs: Tab control style for each screen within an object screen set. This attribute has no effect on screens within a transaction or fetch screen set.
  • Buttons: Button style for all button definitions on all module screens. This includes buttons that appear on built-in Agentry Client screens, and buttons within screen definitions.
  • Focused Buttons: The style to apply to the button that currently has the focus. This includes buttons that appear on built-in Agentry Client screens, and buttons within screen definitions.
Detail Screen Styles
  • Screen: The style to apply to all detail screens defined within the module. This affects all portions of the screen that do not show any fields or buttons.
  • Fields: The style to apply to all fields that appear on a detail screen.
  • Focused Fields: The style to apply to the detail screen field that currently has the focus.
  • Read-Only Fields: The style to apply to a detail screen field that is defined to be read-only. If not specified, the Fields style is applied.
  • Hyperlinks: The style to apply to detail screen field labels that are defined as hyperlinks.
  • In Progress Edit Screens: The style to apply to screens in which changes are currently being made and have not yet been applied. This affects screens displayed in List Tile View and Tile Edit fields.
List Screen Styles
  • Screen: The style to apply to all list screens defined within the module. This affects all portions of the screen not displaying a list, header label, detail pane, or button.
  • Header Label: The style to apply to all list screen header labels. If no header label is defined this attribute has no effect on the screen.
  • Column Labels: The style to apply to the column labels on the screen’s list control. This style is applied to the column labels of any screen containing a list control, including both built-in Agentry Client screens as well as list screen definitions, and list view field definitions.
  • Rows: The style to apply to all rows on a list screen. The Hyperlinks optional style overrides the Rows style for cells with hyperlinks. This style is applied to the list items of any screen containing a list control, including built-in Agentry Client screens, list screen definitions, and list view field definitions.
  • Alternate Rows: The style to apply to every other row in a list, beginning with the second row. The Hyperlinks optional style overrides the Alternate Rows style for every other row where there are cells containing hyperlinks.
  • Highlight Rows: The style to apply to a row to draw attention to it. Do not set this style attribute at the application level. The platform and list screen definition types both contain a Highlight Rows attribute that should be used.
  • Selected Rows: The style to apply to the row or rows currently selected by the user in the list control. The optional Hyperlink style is applied to any cells within the selected row containing a hyperlink.
  • Selected No Focus Row: The style to apply to the row or rows currently selected by the user in the list control, when the input focus is set to some control other than the list control. The optional Hyperlink style is applied to any cells within the selected row containing a hyperlink.
  • Detail Pane: The style to apply to both the foreground (text) and background of a list screen’s detail pane. If no detail pane is defined, this attribute has no effect on the screen.