Units of Work

Tasks are developed to meet different business needs. Tasks that run in the Services Framework receive work requests from the Transaction Server through the Messaging API. The Transaction Server sends unit of work information to a task for processing. Depending on the type of task receiving the initiation request, the unit of work may be for processing a transmission, a batch, a transaction, or business day.

If a task is processing a unit of work, it gets the unit of work information using the getUow() method from the BaseIPDTask. 
public  UOW  getUow();
The unit of work object contains a value and an optional type ID. The type identifies the unit of work value. Examples of type identifiers are:
  • BUSINESS_DAY_ID
  • PAYMENT_ID
  • PRESENTMENT_GROUP_ID
  • PRESENTMENT_ID
  • SEGMENT_ID
  • ENTRY_ID
Note: Depending on how the task was written and its purpose, all tasks may not need a unit of work. This is always the case when a task is scheduled to run on a timed basis using the scheduler. All tasks that are initiated from the scheduler only receive configuration parameters and not a unit of work value.

Refer to the Javadoc information for additional information about methods and signatures.