A transaction server update step references a step definition within the same module that is run during transmit to update the back end system with the data captured by the transaction. This step has access to all of the properties of the transaction using the SDML or mechanisms available using the Agentry Java API. The value of these properties can be used by the steps to update the back end system. An update step can be defined to run or not run based on a data state being set for the transaction. An update step can also define a response to be sent to the Client to perform some additional action in relation to the object instance targeted by the transaction.
Using the data state functionality, update steps may be defined for a single transaction that process the data captured in the transaction normally, and other steps that run only when data states are set to provide data collision handling. Each server update step can contain its own list of selected data states, that is, the data states it is aware of. It can then be defined to run or not when one of its selected data states is set.
Server update steps can send a client response after they have been processed by the Agentry Server. This response will only be sent if the step that defines it is run. Only one response is sent for a transaction. There are different responses possible, and which one is ultimately sent to the Client is based on the type of response.