Arguments of a Task Step

You can define an argument in the Multi Value Property Window (MVPW) pane to pass information in and out of task steps. For example:

To pass the Object Id from a parent task to a subtask, you define input arguments and output arguments for the subtask step.
If a subtask includes a return code of SUCCESS or FAILED, then you can configure Siebel CRM to send the return code to the parent task through an output argument for the subtask step.

You can define input arguments and output arguments for the steps shown in the following table. The Task Step IO Argument is a child object of the task step object that allows you to use an input or output argument on some types of task steps.

Input Argument	Output Argument
You can define an input argument on the following step types: Business Service Siebel Operation Task View Subtask Error	You can define an output argument on the following step types Business Service Siebel Operation Task View Subtask

Input Argument

Output Argument

You can define an input argument on the following step types:

Business Service
Siebel Operation
Task View
Subtask
Error

You can define an output argument on the following step types

Business Service
Siebel Operation
Task View
Subtask

Some operations include predefined outputs:

NumAffRows. Used with a Query operation. Returns the number of rows returned in the query. For more information, see Optional View Technique.
NoMoreRecords. Used with a NextRecord operation. Returns TRUE or FALSE. If no more records are available to process, then it returns TRUE.

For more information about:

Creating arguments, see Creating Arguments for a Task Step.
The task property, see About the Task Property.
Similarities between how a task uses a task property and how a Workflow Process uses a process property, see Siebel Business Process Framework: Workflow Guide.
The Task Step IO Argument object, see Siebel Object Types Reference.