How a Subtask Uses a Task Property

Similar to the subprocess step of a Workflow Process, you can configure Siebel CRM to pass information in and out of a subtask through a task property in an input argument or output argument according to the following logic:

• An input argument allows Siebel CRM to pass data from the parent task into the subtask. If Siebel CRM starts a subtask, then it initializes the task property of the subtask with the value of the input argument of the subtask step in the parent task.

• An output argument allows Siebel CRM to return information from a subtask in the parent task. If the subtask returns data to the parent, then the parent can read the task properties of a subtask through the output argument of the subtask step.

You can use an input argument to pass a system task property, such as the object Id, from a parent task to a subtask. If the subtask references a different business component, then you must configure Siebel CRM to pass the ROW_ID of the target object as the subtask Object Id task property. For a subtask step, the receiving end of an input argument is one of the task properties of the subtask. To choose this value, you can use the list in the Task Input field. The Multi Property Value Window (MPVW) displays the task properties of the subtask that are of type In/Out or In in this list.

If the subtask creates a child object, then the Object Id that Siebel CRM passes to a subtask must be null, and it must not be the Object Id of the parent.

For more information, see Creating a Subtask Step.

Why Siebel CRM Passes Hierarchical Data by Reference

A parent task and a subtask include separate local task properties, so passing arguments causes Siebel CRM to move the data between the parent task and the subtask. Task properties of type Hierarchy are automatically passed by reference (which avoids copying the data) to the subtask. All other types of task properties are passed by value and are copied to the subtask.