Transaction

The transaction definition defines data to be captured on the Agentry Client. As a part of its definition, the transaction includes a target object type, data values to be captured, client-side data validation, and processing its data to the back end system by the Agentry Server during synchronization. Transactions can add new object instances, edit an existing object, delete an object, or modify an complex table or data table record. Each of these behaviors is exhibited by a different transaction type, selected during the creation of the transaction.

A transaction definition is created within the application to target a specific object type within the same module. Transactions are instantiated on the Agentry Client one at a time as the result of the execution of a transaction step within a client action. A transaction instance can target only one instance of an object.

The transaction can be displayed to the user in a screen set, which will behave as a wizard allowing the user to enter data in a series of one or more screens.

There are five different types of transactions that can be defined for an application. Each captures data for a specific type of change on the Agentry Client. The transaction types are:
  • Add: An add transaction type is defined to allow the user to create a new object instance on the Agentry Client.
  • Edit: An edit transaction is defined to allow the user to edit the property values of an existing object instance on the Agentry Client.
  • Delete: A delete transaction is defined to remove an object instance from the Agentry Client.
  • Data Table Change: A data table change transaction is defined to allow the user to add or edit a data table record on the Agentry Client.
  • Complex Table Change: A complex table change transaction is defined to allow the user to add or edit a complex table record stored on the Agentry Client.

Transaction Child Definitions

All transactions, regardless of type, have the same child definitions. The purpose of these child definitions is the same for all transaction types.
  • Properties: A transaction property defines a single piece of data a transaction will capture, including its data type and initial value.
  • Validation Rules: A transaction validation rule defines what rule definition will be used to validate the transaction’s data and how failed validation is handled on the Agentry Client.
  • Server Data State Steps: A transaction server data state step references a step definition within the same module to be run by the Agentry Server to check the back end system for data collisions during transaction processing.
  • Server Update Steps: A transaction server update step references a step definition that is run during transmit to update the back end system with the data captured by the transaction.
  • Error Handling Steps: A transaction error handling step references a step definition that is run during transmit if an error occurs while processing the transaction’s data state or update steps.

Transaction Attributes

Transaction attributes specify the type of transaction, the object type it targets, the key property of the transaction, and the transaction’s name and display name. There are also type-specific attributes for the different transaction types. Review the information on the specific transaction types for details on these attributes.

Parent topic: Module-Level Data Definitions Overview