1. Business Process Framework: Task UI Guide
  2. Subtask Charactieristics

Subtask Charactieristics

A subtask includes the following characteristics:

  • A task can include one or more subtask steps.

  • A subtask can include a subtask.

  • You cannot use a subtask as a parent task.

  • A subtask can include a commit step.

  • An object definition must exist for the subtask before you can reference it in a subtask step of the parent task.

  • The Is Subtask property of the task that a subtask step references must be TRUE. You cannot modify this value after you set it.

  • The boundaries of a subtask are not visible in the Siebel client. For example, if the user clicks Previous or Next, then the user can cross the subtask boundary in either direction.

  • You can define an event handler only for a parent task, and not a subtask. For more information, see How Siebel CRM Handles an Event That Occurs in a Subtask.

  • You must explicitly define a task as the parent task or the subtask at design time. Each parent task includes a task state. The task state stores information that is essential to the run-time task instance. This information includes the pointer to the current step, task object Id, and the navigation path. A subtask does not require an individual task state, but it does require an independent set of local task properties.

  • The parent task and the subtask pass data through input arguments and output arguments so that they can communicate with each other.