Creating Steps and Connectors

This chapter describes how to create task UI steps and connectors. It includes the following topics:

Overview of Step Types

The following image includes the different types of steps and connectors that Siebel Tools displays in the Task Palette of the Task Editor. For more information, see Using the Task Editor.

The following table describes the step types and connectors that are available in the Task Palette.

Table Step Types and Connectors in the Task Palette

Step Type	Description
Start	Defines the input conditions that must be met to run a task instance.
Task View	Displays a task view in the Siebel client.
Siebel Operation	Includes an Insert, Update, or Query operation that interacts with a business component record.
Business Service	Calls a business service that allows you to run a predefined or custom action.
Decision Point	Evaluates a condition to determine the next step to run.
Subtask	Calls a task UI. The subtask task can be independent of the calling task.
Commit	Explicitly saves task data that Siebel CRM stores in temporary storage to the Siebel database.
Error	Creates an error and returns control to the current view.
End	Indicates the end of the task UI.
Connector	Determines the direction of flow between steps in a task UI.
Error Exception	Handles deviation from normal processing, such as a system error or a custom error that you define.

Creating a Start Step

A start step is a type of task UI step that indicates the starting point of a task. A task must include only one start step. You can create conditional logic and run-time events on the connector that emanates from the start step when you create a workflow process. You are not required to create a condition branch that emanates from the start step for a task UI.

To create a start step

Add a start step to a task UI.
For more information, see Adding a Step to a Task UI.

Creating a Task View Step

A task view step is a type of task UI step that displays a task view in the Siebel client. The task view step allows you to map a business process to the user interface. Several properties on the task view step, such as Disable Cancel, allow you to specify behavior of the task playbar and control how Siebel CRM saves information to the Siebel database. For more information, see About the Task View.

To create a task view step

Add a task view step to a task UI.
For more information, see Adding a Step to a Task UI.
Choose the task view step you added in the first step.
In the Properties Window, set the Task View property.
Siebel Tools binds the task view step to a task view. You can double-click the task view step to view and edit the task view. For more information, see Drilling Down on a Task View Step.

You must create the applets and view before you can do this step. If you do not do this, then Siebel Tools does not display any values in the Task View property.
Set the following properties:
- Disable Cancel
- Disable Pause
- Disable Previous
You can set the disable property for the button to TRUE to disable a navigation button. For example, to disable the Cancel button, set the Disable Cancel property to TRUE.
Set the following properties:
1. Display Name
2. Display Name Type
Display Name Type controls how Siebel CRM displays the task step of the current task pane. Siebel CRM uses it and the Display Name property. For more information, see Controlling the Display Name of a Step.
Set the Forward Button Type property.
For more information, see Validation with Forward Navigation in the Task Playbar.
Set the following properties:
- Retain Applet SearchSpec
- Retain Task SearchSpec
- Retain User SearchSpec
Search specifications affect how Siebel CRM preserves the business component state across task views. For more information, see Record Context Is Lost and Siebel Object Types Reference.
Optional. Set the Task Step Context property.
The Task Step Context property defines the search specification that Siebel CRM uses to filter data for the view step. For more information, see Defining the Context for a Task Step.
Optional. If you create the task step context, then you can add output arguments, as required.
The task view step does not return an output argument. You can use the Output Arguments tab in the Multi Value Property Window to update a task property. For example, you can copy data that the user enters in a business component field to a task property. For more information, see How the Type Field Affects Other Fields in the Multi Value Property Window.
Choose the File menu, and then choose the Save menu item.

Drilling Down on a Task View Step

You configure Siebel CRM to bind the task view step to a task view. You can then double-click the task view step in the Task Editor, and then Siebel Tools displays the Task View UI editor that displays the view that it binds to the task view step. The Task View UI editor displays an approximation of how Siebel CRM renders the view at run time.

Disabling the Pause Button

You can set the Disable Pause property on the task view step to TRUE to disable the Pause button on the playbar. Disabling the pause button does not prevent implicit pause, but you can use it to provide a hint to the user that pausing is not recommended. For example, in a summary view. For more information, see Task Pause with the Task Playbar.

Controlling the Display Name of a Step

You can use the Display Name and Display Name Type properties of the task view object to suppress steps that Siebel CRM displays in the current task pane. If you set Display Name Type to Unique, and if consecutive task views use the same display name, then Siebel CRM displays this name only one time in the current task pane.

To control the display name of a step

Do one of the following:
- Enter a value in the Display Name property for the first step. Leave Display Name empty for subsequent steps.
  If the Display Name property is empty in subsequent steps, then Siebel CRM displays the step for the first view as the current step even if the user navigates to a subsequent step. This option is useful if the user must perceive a series of views as one logical step.
- Set the Display Name Type property to Unique.
  For more information, see Using the Display Name with a Looping Task UI.

Using the Display Name with a Looping Task UI

Setting the Display Name Type property to Unique causes Siebel CRM to add the value that the Display Name property contains to the current task pane the first time the user encounters the step. Siebel CRM does not add it on a subsequent step. This configuration is useful in a loop. For example, a loop where the user enters multiple line items, where each line item represents one iteration of the loop. If the type is set to Unique, then Siebel CRM displays the step in the current task pane the first time through the loop, but not during subsequent iterations.

If a loop includes:

One view. Setting the Display Name Type property to unique is sufficient.
More than one view. You can set the Display Name Type property to Unique and leave the Display Name property empty. Siebel CRM completes the Display Name and marks it as Unique for the first view in the loop. Other views in the loop include an empty Display Name. Siebel CRM then displays the Display Name of the first view in the current task pane for the entire loop.

For more information, see Siebel Object Types Reference.

Creating a Siebel Operation Step

A Siebel operation step is a type of task UI step that performs an operation on business component data. Example operations include Insert, Update, and Query. Siebel CRM runs a Siebel operation step, and then the Siebel Operation Object ID process property stores the row ID of the record where Siebel CRM performed the operation. If the query operation returns multiple records, then the property stores an asterisk (*).

You can create a Siebel operation step for a business component that references the same business object that the task UI references. To update a business component that does not reference this business object, you must use Siebel Tools to configure the business component to reference the business object.

Some business component fields are not available for modification. For more information, see Business Component Fields That a Task UI Can Modify.

To create a Siebel operation step

Add a Siebel operation step to a task UI.
For more information, see Adding a Step to a Task UI.
In the Properties window, set the Operation property.
If you must configure Siebel CRM to update or insert a field that includes dependencies, then make sure the field is valid. For example, if your task UI updates the area and subarea fields of a service request, then you must make sure the value that the user chooses for the subarea field is valid for the area field. For more information, see Siebel Business Process Framework: Workflow Guide.
In the Business Component property, choose the business component where this Siebel operation step uses data.
If you must configure Siebel CRM to create a field, or if the Siebel operation step performs an insert operation, then make sure you add the field to the Siebel operation step.
For more information, see Identifying the Business Component Field for a Siebel Operation Step.
Optional. Create a search specification for the Siebel operation step.
For more information, see Defining the Context for a Task Step.
Optional. In the Multi Value Property Window, add input arguments and output arguments.
For more information, see Creating an Output Argument on a Task Step.

About the Defer Write Record Property

Setting the Defer Write Record property to TRUE on a Siebel operation step allows the user to provide data for a required field in the subsequent task view step before the Siebel operation step attempts an insert. If the user attempts to provide data for a Siebel operation that already occurred, then Siebel CRM displays an error that a required field includes no data. This situation occurs when the following logic exists in your task UI:

A Siebel operation step performs an insert operation.
Task view step follows the Siebel operation in the first step. The user uses this task view step to provide the data that the insert requires.

To fix this problem, the Defer Write Record property defers the insert operation until a commit operation occurs that allows the user to provide the required data before Siebel CRM does the insert operation. The Defer Write Record property is not specific to a task UI. For more information, see Using the Defer Write Record Property When You Disable Task Transaction and Siebel Object Types Reference.

Identifying the Business Component Field for a Siebel Operation Step

You can use the Fields tab in the Multi Value Property Window to create a field for a Siebel operation step.

To identify the business component field for a Siebel operation step

Open the Task Editor.
For more information, Opening the Task Editor.
Make sure the Business Component property of the Siebel operation step you must modify contains a value.
Choose the Siebel operation step, and then open the Multi Value Property Window.
In the Multi Value Property Window, click the Fields tab.
Right-click in the list area of the Multi Value Property Window, and then choose New Record.
In the Field Name field, choose the business component field that this step must update.
The dropdown list for the Field Name field lists the business component fields for the business component that you specify in the Business Component property of the Siebel operation step.
Set the Type field.
For more information, see How the Type Field Affects Other Fields in the Multi Value Property Window.
Set the Value field.
If you create multiple fields, and if the user must enter field values in a specific order, then define this order in the Preferred Sequence field, beginning with number 1.
Optional. Enter comments.

For information about updating a field that uses a multivalue group, see Siebel Business Process Framework: Workflow Guide.

Creating a Business Service Step

A business service step is a type of task UI step that calls a business service. The following items describe actions that some predefined business services perform:

Notification. The Outbound Communication Server business service sends a notification to an employee or a contact.
Assignment. Assignment Manager calls the Synchronous Assignment Manager Request business service to assign an object in a task UI.
Server task. You can use one of the following business services to run a server task for a server component:
- Synchronous Server Requests business service
- Asynchronous Server Requests business service

For more information about business services, see the following items:

Guidelines for Using a Business Service
Siebel Business Process Framework: Workflow Guide

To create a business service step

Add a business service step to a task UI.
For more information, see Adding a Step to a Task UI.
In the Business Service Name property, choose the name of the business service that this step calls.
In the Business Service Method property, choose the method that Siebel CRM uses to call the business service.
The choices that Siebel Tools displays for this property depend on the business service that you define in the previous step.
Create input arguments and output arguments.
For more information, see How the Type Field Affects Other Fields in the Multi Value Property Window.

Creating a Decision Point

A decision point is a type of task UI step that evaluates one or more conditions to determine the next step to run in a task. You can create a condition on a connector that emanates from the decision point. You cannot create a condition directly on the decision point.

To create a decision point

Add a decision point to a task UI.
For more information, see Adding a Step to a Task UI.
Create a branch connector for the decision point.
For more information, see Creating a Branch Connector.

Creating a Subtask Step

A subtask step is a type of task UI step that allows you to start a separate task in a task. You can use it to do the following:

Reuse common sequences that you define in a task UI to decrease development and maintenance cost.
Modularize a task UI. If a task is so large that it becomes difficult to develop and manage, then you can separate it into smaller subtasks.
Separate a large task into multiple tasks to improve readability of the task UI in the Task Editor.
Maintain a clean, consistent, and intuitive programming model.

For more information, see Using a Transient Business Component in a Subtask.

To create a subtask step

In the Object Explorer, click Task.
Make sure the subtask that the subtask step calls is defined correctly.
For more information, see Characteristics of a Subtask.
Add a subtask step to a task UI.
For more information, see Adding a Step to a Task UI.
In the Subtask Name property, choose the subtask that this subtask step calls.
Optional. Create input arguments or output arguments for the subtask.
For more information, see How the Type Field Affects Other Fields in the Multi Value Property Window.

Comparing a Subtask to a Subprocess

The following table compares a subtask that resides in a task UI to a subprocess that resides in a workflow process.

Table Comparison of Subtask to Subprocess

Object	Siebel Task UI	Workflow Process
Process Instance	A parent task UI 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 UI 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 UI 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.

Characteristics of a Subtask

A subtask includes the following characteristics:

A task UI 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 UI 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 UI as the parent task or the subtask at design time. Each parent task UI 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.
You can deploy and activate a subtask in the same way that you deploy and activate a parent task. If you publish a task that includes a subtask, then you must publish the subtask before you publish the parent task. This sequence makes sure the subtask is available to the parent task in the run-time environment.

Using the Exception Branch in a Subtask

You can use an exception branch in a subtask. You cannot use an exception branch to enter or leave a subtask step. This restriction makes sure that a subtask can only exit from the end step of the subtask, and in the forward direction.

Creating a Commit Step

A commit step is a type of task UI step that explicitly saves task data from temporary storage to the Siebel database. The end step also saves temporary data to the Siebel database when a task finishes. The commit step allows you to configure Siebel CRM to save data before the task reaches the end step. You can create an exception branch that emanates from the commit step to handle an error that results from persistent temporary data.

You must use a commit step in the following situations:

To save data at an intermediate save point
To make sure the user cannot modify some data

For more information, see Commit Interim Data Technique, and Using a Transient Business Component with a Commit Step.

To create a commit step

Add a commit step to a task UI.
For more information, see Adding a Step to a Task UI.

Creating an Error Step

An error step is a type of task UI step that creates an error message and returns control to the current view. It allows you to configure Siebel CRM to display an error message in the Siebel client. This functionality is typically required if an error message that a business service returns is not sufficiently clear to the user. The error step in a task UI supports an exception in a way that is similar to how the Stop step works in a workflow process. For example, assume a business service step in a task UI calls an external system, the external system is down, and an error occurs. An exception branch and an error step handle this error.

If the error step runs, then Siebel CRM does the following work:

Replaces the existing error message with the error message that you define for the error step. This configuration allows you to display an informative and contextual message in the Siebel client. Siebel CRM displays this error message in a dialog box which opens in the current view.
Resets the task UI to the most recent view step that it displayed before it encountered the error step. If Siebel CRM runs an error step before it displays the first view step in a task UI, then it cancels the task.

You can use an error step in an exception branch or as part of the normal logic of a task UI to handle an expected error.

To create an error step

Add an error step to a task UI.
For more information, see Adding a Step to a Task UI.
In the Error Code property of the error step, choose a predefined error code from the picklist, or define a custom error message.
For more information, see Creating a Custom Error Message.

How Siebel CRM Handles an Error While a Task UI Runs

If an exception occurs in a task step while the task UI runs, and if no exception branch is defined, then Siebel CRM displays a generic error message in a dialog box that opens in the current task view. The user can acknowledge the error message, and then correct the data in the task view, or can navigate to a previous task view to correct the data. This configuration is known as default exception handling.

How Siebel CRM Handles an Error When the User Pauses a Task UI

No exception handling occurs if a user pauses a task UI. If a paused task fails, then Siebel CRM displays a typical error message, not a pause error. The user can cancel or continue the task.

How Siebel CRM Handles an Error When the User Cancels a Task UI

If the user clicks Cancel, then Siebel CRM displays a dialog box that prompts the user for confirmation. For example, if the user is about to perform a delete or undo operation in a task UI, and then clicks OK to continue.

Creating a Custom Error Message

You can use a custom error code and an input argument to create a custom error message for an error step. You can use the input argument to define the text of the custom error message.

To create a custom error message

Add an error step to a task UI.
For more information, see Adding a Step to a Task UI.
In the Error Code property of the error step, choose an error code that starts with WF_ERR_CUSTOM.
For example, WF_ERR_CUSTOM_1.
Make sure the error step is chosen.
Use the Multi Value Property Window to add an input argument:
1. In the Input Argument field, enter a substitution variable.
  
  For example, %1. You can use a substitution variable in the error message to represent the input argument for an error step. A percent symbol (%) identifies a substitution variable.
2. Choose a Type for the input argument, which is the source of the value that Siebel CRM uses for the error message text.
3. Define the remaining fields, according to the Type you set in the previous substep.
  
  For more information, see Creating an Input Argument on a Task Step.
4. Step off the record to save the modifications.
Optional. Repeat the previous step to create more input arguments.

Creating an End Step

The end step is a type of task UI step that instructs Siebel CRM to end the task instance, and then to transfer data that currently resides in temporary storage to the Siebel database. It also provides one last chance to modify a task property that the task output arguments return from the object that called the task. Each task must include only one end step.

To create an end step

Add an end step to a task UI.
For more information, see Adding a Step to a Task UI.
Optional. Define an output argument for the end step.
An output argument allows you to configure Siebel CRM to store a value that it creates while a task UI runs. It stores this value in a task property. It can then pass this value between objects in a task UI, such as between a subtask and a parent task. For more information, see About the Task Property.

Creating a Connector

The connector is an object in a task UI that allows you to establish flow between task steps.

To create a connector

Add a connector to a task UI.
Do the work described in Adding a Step to a Task UI, with the following differences:
- Instead of selecting and moving a step type, select and then move a connector.
- When you select and move the connector from the Task Palette to the canvas, place the start point of the connector onto the preceding step.
- Before you connect two steps, place the steps to be connected on a horizontal plane, with the preceding step placed first and the subsequent step placed second. Place the steps in close proximity to one another. Siebel Tools automatically connects the start point to the preceding step and the end point to the subsequent step when you drop the connector.
Select and move the connector end point onto the subsequent step.
A connector end point includes an arrow.

A connector end point that is hollow (colored white) is not connected correctly. A solid end point (colored red) indicates that the connector is connected correctly. You must make sure the ends of every connector in the task UI are solid (colored red).
Optional. Enter text in the Label property.
Siebel Tools displays this text as a label on the connector in the Task Editor.

Creating a Branch Connector

A branch connector is a type of connector in a task UI where you create a condition. Similar to how it operates in a workflow process, a branch connector in a task UI can be conditional or nonconditional. Siebel CRM uses a condition and a decision point to determine the path to follow in the task UI according to criteria that you define. A different action can occur depending on the path that it follows.

You can configure branching in a task UI on branch connectors that emanate from a decision point. You can create a separate condition for each of these connectors. You do not create conditions on the decision point. To determine the next step to run, the decision point evaluates the conditions you define on the outgoing connectors.

You can define the following values in the Type property of a connector:

Condition. Includes a condition. Allows you to create a condition that must be met to continue through this path.
Default. Does not include a condition. If the condition is not met for another connector, then the task UI flows down the Default connector.

To view an example that includes a condition, see Revising the Task UI.

To create a branch connector

Create a connector.
For more information, see Creating a Connector.
Enter or modify the Name property of the branch connector.
The branch name must be unique.
Set the Type property of the branch connector to Condition.
For more information, see the description for the task branch object in Siebel Object Types Reference.
Create conditions that apply to this branch.
For more information, see Creating a Condition on a Branch Connector.
In the Comments property, enter text that describes the branch logic.
Optional. Repeat all of the previous steps for each additional branch connector you must create.
If your task UI must proceed along more than one conditional connector and one default connector, then you must create a separate branch connector for each logical path.
Create a default branch.

Caution: You must create a Default connector to handle the situation where an item does not meet any of the conditions you create.

Creating a Condition on a Branch Connector

You can create a condition on a branch connector to control task flow. For example, the following are some conditions that you can create according to the value of a priority field:

If the priority is high, then the task UI follows a branch that sends an email to a vice president.
If the priority is medium, then the task UI follows a branch that sends an email to an individual contributor.

You can use the Compose Condition Criteria dialog box to create a condition. For detailed usage information, see Siebel Business Process Framework: Workflow Guide.

To create a condition on a branch connector

Open the Task Editor.
For more information, Opening the Task Editor.
In the Task Editor, right-click the branch connector where you must create a condition.
Choose Edit Conditions.
Siebel Tools displays the Compose Condition Criteria dialog box. Siebel Tools constrains the Values that it lists in this dialog box according to the business object that the Business Object property of the task UI references.

In the Compose Condition Criteria dialog box, use the Compare To list to choose one of the values that the following table describes.

Value	Description
Applet	Uses the value that an applet field contains for the condition comparison.
Business Component	Uses the value that a business component field contains for the condition comparison or when you create an expression.
Expression	Uses an expression to evaluate a specific value.
Task Property	Compares the value that a task property of a task instance contains to a defined value.

Choose an Operation to evaluate the values.
Enter an Object and Field, if necessary.
Enter one or more values in the Values window.
You can enter multiple values in the Values window. If you enter multiple values, then Siebel CRM uses an OR operator between each value.
If you chose Expression in the Compare To field, then enter the expression in the Values window.
For more information, see Siebel Developer's Reference.
Click OK.
Save your modifications.
Close the Task Editor.

Creating Multiple OR Conditions

You can create multiple conditions for each branch. Siebel CRM treats multiple conditions with the AND operator. You can use multiple expressions to create multiple OR conditions. The following example illustrates an expression that uses the OR operator to compare a business component field to the date for today:

([Close Date] <= Today()) OR ([Name] = 'Opportunity test1')

For more information, see Siebel Business Process Framework: Workflow Guide.

Branching and Parallel Processing

You cannot define the order that Siebel CRM uses to evaluate conditions, so it is important that you define branching conditions so that they are mutually exclusive. Siebel Task UI does not support parallel processing. Make sure you create conditions so the task UI can proceed along only one connector. If you create conditions so that flow can proceed simultaneously along multiple connectors, then Siebel CRM cannot predict run-time behavior.

Creating an Error Exception Connector

The error exception is a type of connector that resides in a task UI. It handles the following types of errors:

System. For example, a failure that occurs when Siebel CRM sends an email notification.
User. For example, a user attempts to submit an incomplete order.

Siebel Tools displays any error exceptions in a different color (that is, as a red connector) in the Task Editor.

To create an error exception

Create a connector.
For more information, see Creating a Connector.
In the Type property of the connector, choose one of the following values:
- Error Exception
- User Defined Exception
The task controller treats a user defined exception the same way it treats an error exception.
Double-click the exception connector.
In the Compose Condition Criteria dialog box, create conditions that apply to the exception.
For information about how to use the Compose Condition Criteria dialog box, see Siebel Business Process Framework: Workflow Guide.

Creating the Arguments of a Task Step

This topic describes how to create the arguments of a task step. For more information, see Arguments of a Task Step.

Creating an Input Argument on a Task Step

An input argument allows you to configure Siebel CRM to pass data to some types of steps in a task UI at run time.

To create an input argument on a task step

Open the Task Editor for the task UI you must modify.
For more information, Opening the Task Editor.
In the Task Editor, choose the step where you must create an input argument.
In the Multi Value Property Window, click the Input Arguments tab.
For a Siebel operation step, you use the Fields tab rather than the Input Arguments tab.
Right-click in the list area of the Multi Value Property Window, and then choose New Record.
In the Input Argument field, choose an input argument.
This value is the destination of the input argument. For a Siebel operation step, choose the Field Name.
In the Type field, choose a type.
Define remaining fields for the input argument, according to the type you defined in the previous step.
For more information, see How the Type Field Affects Other Fields in the Multi Value Property Window.
Some fields are not available. For more information, see Business Component Fields That a Task UI Can Modify.

Creating an Output Argument on a Task Step

An output argument allows you to configure Siebel CRM to store the value that results from processing one of the following step types:

Business service step
Siebel operation step
Task view step
End step

Siebel CRM stores this value in a task property. It can then pass this value to another object, such as the input argument of a subsequent task step.

To create an output argument on a task step

Open the Task Editor for the task UI you must modify.
For more information, Opening the Task Editor.
In the Task Editor, choose the step where you must create an output argument.
In the Multi Value Property Window, click the Output Arguments tab.
Right-click in the list area of the Multi Value Property Window, and then choose New Record.
In the Property Name field, choose a property name.
This is the name of the task property that stores the value of the output argument.
In the Type field, choose a type.
Define remaining fields for the output argument, according to the type you defined in the previous step.
For more information, see How the Type Field Affects Other Fields in the Multi Value Property Window.

Creating a Task Property

A task property can pass a value between objects in a task flow, such as between a task step and another task step, or between a task step and a subtask. Siebel Tools automatically defines a set of system task properties when you create a task object. You can use these system task properties to pass information between task objects. You can also define a custom task property to meet your design requirements. For more information, see About the Task Property.

To create a task property

Open the Task Editor.
For more information, Opening the Task Editor.
Click the canvas. Do not click a task step or connector.
The Multi Value Property Window displays tabs that are specific to the task UI.
In the Multi Value Property Window, click the Task Properties tab.
Right-click in the list area of the Multi Value Property Window, and then choose New Record.
Enter a value in the Name field.
Choose the Data Type for the task property.
Optional. In the Default field, assign a default value for the task property.
Optional. Modify the value in the following fields:
- Access Mode
- In/Out
  Siebel Tools sets the value in the Access Mode field to R/W and the value in the In/Out field to None, by default. Typically, you do not need to modify these values. However, you can make modifications according to the following items:
- You can modify the Access Mode field to make the task property read only.
- You can modify the In/Out field to one of the following values:
  - In
  - Out
  - In/Out
    The In/Out field allows you to use the task property as input, output, or input and output for the task UI. The default value is None. This configuration confines the task property to the task instance.
If you chose Integration Object as the Data Type in the step to choose the data step, then choose the Integration Object that Siebel CRM must use for the task property.
Optional. Enter comments in the Comments field, as necessary.
Step off the record to save your modifications.