Allocate Task Time-Triggered Transaction

To create tasks as Draft, set the flag "Delayed Inventory Allocation Support" at the node level to "Y". This flag is available in the "Wave Release Schedule" for pick planning.

Sterling Selling and Fulfillment Foundation provides draft status support for outbound picking, retrieval, and putaway tasks. When tasks are created in large numbers as a part of wave or move request release, locks are held for longer durations (for creating all tasks). In such situations, you can enable the draft status support to allocate tasks in a multi-threaded fashion by the Allocate Task agent. This reduces the lock holding time.

Attributes

The following are the attributes for this time-triggered transaction:

Table 1. Allocate Task Attributes
Attribute Value
Transaction Name Allocate Task
Transaction ID ALLOCATE_TASK
Base Process Type Task Execution
Base Document Type Task Execution
Abstract Transaction No
APIs Called None
User Exits Called None

Criteria Parameters

The following are the criteria parameters for this transaction:

Table 2. Allocate Task Criteria Parameters
Parameter Description
Action Required. Triggers the transaction. If left blank, it defaults to Get, the only valid value.
Number of Records To Buffer Optional. Number of records to retrieve and process at one time. If left blank or specified as 0 (zero), it defaults to 5000.
ColonyID Required in a multischema deployment where a table may exist in multiple schemas. Runs the agent for the colony.

Events Raised

The following events are raised by this time-triggered transaction:

Table 3. Events Raised by the Allocate Task Transaction
Transaction/Event Key Data Data Published Template Support?
ALLOCATE_TASK / CHILD_ALLOCATION_COMPLETE task_dbd.txt ALLOCATE_TASK.ON_CHILD_ALLOCATION_COMPLETE.xml Yes
Note: The ALLOCATE_TASK.ON_CHILD_ALLOCATION_COMPLETE event publishes information of the summary task for which allocation of all child tasks is complete. Use this event to print batch sheets or task lists for picking against move requests. Otherwise, if you do not use the draft status feature, the batch sheets of task lists would be printed on the RELEASE_MOVE_REQUEST.ON_SUCCESS event.

Define a custom service which does the following:

  1. Calls the getTaskDetails API.
  2. Using an XSL, prepares input to getMoveRequestDetails API by extracting MoveRequestKey from the TaskReferences node.
  3. Calls the getMoveRequestDetails API and connect the output to the PrintMoveTickets service (provided out-of-the-box).