Comparing a Subtask to a Subprocess

The following table compares a subtask that resides in a task to a subprocess that resides in a Workflow Process.

Object	Task UI	Workflow Process
Process Instance	A parent task and a subtask share the same process instance.	A parent Workflow Process and a subprocess run in separate instances.
Process Properties and Task Properties	Starting a subtask does not create a new instance. Siebel CRM creates a new context each time it starts a subtask. The context stores local task properties. A subtask and a parent task do not share task properties. For more information, see How a Subtask Uses a Task Property.	Starting a subprocess creates a new instance of the Workflow Process. A subprocess includes an independent set of process properties.
Business Object	A parent task and a subtask must reference the same business object. They must include the same business object type and share the same business object instance.	A parent Workflow Process and a subprocess can reference different business objects, and can use two different business object instances.
Input Arguments and Output Arguments	Siebel CRM can pass information in and out of a subtask through an input argument or an output argument. An input argument allows it to enter data in the task property of a subtask. It can get this data from the parent task. For more information, see How a Subtask Uses a Task Property.	The operation of an input argument or output argument is similar to the subprocess step in a Workflow Process.