An operation is the entity responsible for performing the set of tasks needed to complete a basic financial operation, including data input and validation, interaction with external services, and management of the results and data received. An operation has a requester that requests its execution, provides input data, and eventually receives the results.
The class is responsible for initializing all operation configurations. The class is packaged in bttcore.jar.
<field id="extFile" value="operation.xml" description="The recommended location is under same folder of btt.xml"/>
The extended file contains the operation definitions for the application. By default, the extended file is in the same folder with btt.xml.
<kColl id="classTable">
The classTable contains a collection of definitions for the keywords of operation and their implemented class. Those definitions can be added and removed from the collection. Only those definitions in the classTable collection could be used to define its operation in extended file.
An operation step is an entity that represents one or more actions performed inside an operation. An operation can invoked one or more operation steps during its operation flow to perform some or all of the actions that the operation is to perform. The above configuration item is about opStep tag attributes for a comparison operation step (CompareAssertion).