Work Plan Control

To access the Work Plan Control configuration, select Business Rules > Local Services > WorkPlansService > servername > Control. This displays the Control window.

When the engine is in a paused or stopped state it does not execute tasks. This includes setting manual tasks to "In Progress" when prerequisite tasks are set to Complete.

The following is a list of the behaviors of the various subsystems in reaction to clicking the Start, Pause, or Stop buttons:

• When the engine is in a stopped state and you click Start:

  • Task processing – If the status of a task is changed, then the event for that status is fired and the processor, if any, is executed.

  • Plan processing – If a plan or any task within that plan is changed, the engine reviews and updates, if necessary, the statuses of the tasks and the status of the engine. If it changes a status of a task, then it turns the task over to the task processing subsystem to process that task.

  • Resuming – The engine checks for task phases that were queued for execution when it was shut down and queues them for execution again. When this work is complete, the resuming subsystem shuts down.

  • Polling – The engine checks periodically for timed-out tasks. If it finds any, it tells the task processing subsystem about them.

• When the engine is running and you click Pause:

  • Task Processing – Processing of currently executing jobs is completed. Queued jobs are not started. New jobs are queued for execution but not started.

  • Plan Processing – Same as Task Processing.

  • Resuming – If the resuming thread has already completed, nothing happens. Otherwise, the system finishes running the query to find tasks jobs to resume; and stops reading records from the query and queuing task phases. The record set from the query is kept open.

  • Polling – Polling thread is signaled to stop. If it doesn't stop shortly, the worker thread is aborted.

• When the engine is paused and you click Start:

  • Task Processing – Processing of jobs in the work queue is resumed.

  • Plan Processing – Same as Task Processing

  • Resuming – If it was working when it paused, the thread resumes reading the record set. Otherwise, nothing happens.

  • Polling – The engine checks periodically for timed-out tasks. If it finds any, it tells the task processing subsystem about them.

• When you click Stop:

  • Task Processing – Processing of currently executing jobs is completed. The job queue is emptied and new job requests are ignored.

  • Plan Processing – Same as task processing

  • Resuming – The resuming thread is signaled to stop. If it doesn't stop shortly, the worker thread is aborted.

  • Polling – Polling thread is signaled to stop. If it doesn't stop shortly, the worker thread is aborted.