Every base process type has a set of base transactions defined for it. A transaction is a logical unit of work that is necessary for performing activity within Sterling Order Management System.
Base transactions are predefined transactions that contain information about how the transaction behaves, such as how many copies of a transaction can be kept in a process type and whether or not it can have configurable base pick and drop statuses. Base transactions can be used to create new transactions. These transactions can be changed within the limits defined in the base transaction.
In Sterling Order Management System, APIs are used to complete transactions. When an API is invoked, the Transaction ID is determined based on the context that the API was completed. The transaction ID identifies the transaction to be completed. Depending on the situation, the transaction ID can be passed as an input parameter or it can be pre-defined for the invoking API. For more information about APIs, see the IBM Sterling Order Management: Javadoc.
Transactions can be classified as one or more of the following types:
An externally-triggered transaction is performed through the Sterling Order Management System Services Definition Framework (SDF) which calls a corresponding API within Sterling Order Management System to complete the transaction.
A user-triggered transaction is performed based on user actions performed in the Sterling Order Management System user interface, configured alert queue, or an e-mail exchange.
A time-triggered transaction is performed on scheduled intervals. In Sterling Order Management System, a time-triggered transaction is also called an agent.