Defining detailed information of operation in transaction editor
The operation is an entity that is responsible for performing a set of tasks that are needed to complete a basic financial operation. You can define the attributes of the operation based on your business logic.
Attributes of operation
Id
The name of the operation step. It is a mandatory attribute.
ImplClass
The name of the class the toolkit is to instantiate if the tag name is "operation". This value overrides any definition for the operation in the toolkit definition file.
Context
The name of the operation context.
XVal
The name of the class that implements the process for validating a cross business operation. This class must implement the OperationXValidate interface. By providing a specific class that implements the business validation for the concrete operation, the applications can use a generic operation class for more than one business operation yet start a concrete validation that can be specific to each operation.
Scope
The implementation model for caching operation data. UDTT provides the following scopes:
▪ Request Scope: If you do not specify any scope in the operation definition, operation data is disposed after the request.
▪ Flow Scope: The result is stored at flow context level and destroyed along with Flow Processor. Flow scope also supports flow level failover.
▪ Session Scope: The result is stored along with SessionContext and has same lifecycle.
▪ Application Scope: The result is cached in root Context level by default scope manager and opens for extension.
▪ Customization Scope: UDTT provides extension points for cache customization. Customization scope is an extension point in btt.xml settings section. You can override the eligibility and potential of cache in the original results and define a new scope based on your business logic.
Expire Time
The expiration time of operation cache. The default value is 0, which means that the result never expires. You can define the expiration time in seconds according to your business requirements. You can also define further expiration control features in ScopeManager extensions, for example, the result expires at a given time or times of day.