Monitoring PolicyCenter processes for completion

Night-time processing frequently requires chaining, meaning that the completion of one type of process starts another type of follow-on process. Regardless of implementation mode – work queue or batch process – you most likely must develop custom process completion logic for your type of nightly batch processing.

Characteristics of a completed process run vary depending on the implementation mode:

Work queues: Complete if no work items for a batch remain in the work queue, other than work items that failed
Batch processes: Complete if the batch process stopped and its process history is available

In the base PolicyCenter configuration, Guidewire provides an IBatchCompletedNotification interface that you can implement and call from the Process Completion Monitor process.

public interface IBatchCompletedNotification extends InternalPlugin {
  void completed(ProcessHistory var1, int var2);
}

The completed method takes the following parameters.

`var1`	Process history
`var2`	Number of failed work items

In your implementation of this interface, override the completed method to perform specific actions after a work queue or batch process completes a batch of work. Add a case clause to the method for your type of custom batch processing by specifying its typecode from the BatchProcessType typelist, for example:

switch(type) {
  case BatchProcessType.TC_ACTIVITYESC:
    return new ActivityEscalationWorkQueue()
  case BatchProcessType.TC_MYCUSTOMBATCHPROCESS:
    return new MyCustomBatchProcess()
  ...
  default:
    return null
}