An action defines navigation and user interaction for the Agentry Client. Actions are composed of a series of action steps of varying types. An action is defined to allow the user to interact with the application in some way.
The action defines the object its steps will act upon, any may also define whether or not users will be permitted to cancel the action once it has been executed, and also an optional separate action to execute if the action is cancelled.
The behavior of the action is dictated primarily by its child action step definitions. There are different types of action steps for different types of Agentry Client behaviors. Each action step defines a specific task to be performed on the Agentry Client.
Actions can be referenced by several different components of the user interface, such as buttons, list screens, and others. Whenever an action is executed it will be passed an object instance. This object instance is determined by the user interface component executing the action. The action must be defined for an object type. This object type for the action and the type of object passed to the action on the Agentry Client must be the same. The exception this is when the action is not defined for any object. Such actions are limited in use and normally pertain to performing transmits between the Agentry Client and Agentry Server, or actions that close screen sets but do not open others.
Action Step: An action step defines a single task within an action that is a part of the overall action execution on the Agentry Client.