Process work order hold type

This time-triggered transaction is identical to the Process Order Hold Type transaction, but it is used for work orders instead.

Attributes

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

The following are the criteria parameters for this transaction:

Table 2. Process work order hold type 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.
Next Task Queue Interval	Optional. Specifies in hours how long a failed task should be suspended before it is considered for reprocessing. Defaults to 5 hours.
ColonyID	Required in a sharded deployment where a table may exist in multiple schemas. Runs the agent for the colony.
Task Queue Filter Criteria	Optional. Determines the jobs to be fetched by the agent. The value assigned to this parameter is matched against the custom value stored in the `FILTER_CRITERIA` column of `YFS_TASK_Q` table, while fetching the jobs. Note: `VOID` is a valid task queue filter criteria value which is used to match records with NULL value in the `FILTER_CRITERIA` column of `YFS_TASK_Q` table. For more information, see Workload segregation for task queue agents.

None.

None

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

Table 3. Events raised by process work order hold type transaction
Transaction/Event	Raised when...	Key Data	Data Published	Template Support?
ON_SUCCESS	On success	workOrder_ dbd.txt	VAS_MODIFY_ WORK_ORDER .ON_SUCCESS. xml	Yes *
ON_HOLD_TYPE_ STATUS_ CHANGE	The status of a hold type is changed.	workOrder_ \|dbd.txt	VAS_ON_HOLD _TYPE_STATUS _CHANGE.xml	Yes
* Note: Some of the elements and attributes are not template driven. Refer to the xml for elements level details.