Siebel Business Process Framework: Task UI Guide > Configuring Task UI > Editing Task Flows >

Configuring Task View Steps

A Task View step is used to represent the step in the task flow where a Siebel view is presented to the end user. As an application developer, you can navigate from this Task View step in the Task Designer to the Task View UI editor. You can also bring up the run-time view from this step. See the Siebel Object Types Reference for descriptions of the properties of the Task View Step object.

Adding a Task View Step to a Task

The procedure for adding a task view step is similar to adding any type of step.

To add a task view step

1. Open the appropriate task in the Task Designer.
2. From the Task Palette, drag a Task View step, and drop it on the Task Designer at the desired location.
3. Bind the new task view step to a task view:
   1. Click to select the task view step in the Task Designer.
   2. In the Properties window, select a task view for the Task View property.
4. Select the appropriate settings for the Disable Cancel, Disable Pause, and Disable Previous properties.

   If you want to disable any of the navigation buttons set the corresponding property to TRUE.

5. Enter a Display Name, and pick a Display Name Type.

   The Display Name Type controls the display of the task steps in the Current Task pane. It is used in conjunction with the Display Name property. If set to Unique, consecutive task views with display names of the same value are displayed only once in the Current Task pane (see Controlling Step Display).

6. Select a Forward Button Type.

   The Forward Button Type property determines the label and type of the forward button (Next, Submit or Finish).

7. Select the appropriate settings for the Retain Applet SearchSpec, Retain Task SearchSpec, and Retain User SearchSpec properties.

   See the Siebel Object Types Reference for descriptions of these properties. See also Record Context Is Lost to understand how these settings can affect the way business component states are preserved across task views.

8. (Optional) You can add a Task Step Context to identify the search specification that is applied to filter the data on which the view step is performed.

   For information on how to configure Task Step Context, see Configuring Task Step Context.

9. (Optional) After configuring the task step context, you can add output arguments as needed.

   The task view step does not return output arguments. However, you can use the Output Arguments tab (in the Multi Value Property Window) to configure updates to task properties. For example, you can copy data entered by the end user through a business component field to a task property. For more information on output arguments, see Configuring Input and Output Arguments for Task Steps.

10. Make sure you save your changes before leaving the Task Designer.

Drilling Down on Task View Steps

After you have bound the task view step to a task view, you can drill down on the task view layout by double-clicking on the task view step in the Task Designer. This displays the Task View UI editor, which you can use to edit the task view. You can also display the run-time appearance of the view from the Task View UI editor.