Siebel Business Process Framework: Task UI Guide > Defining Steps and Connectors >

Defining a Task View Step

A task view step is a type of step in a task UI that presents a task view to the end user. 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 as well as control how information is saved to the database.

For more information, see About the Task View.

To define a task view step

1. Add a task view step to a task UI.

   For more information, see Adding a Step to a Task UI.

2. Choose the task view step you added in Step 1.
3. In the Properties Window, choose a task view for the Task View property.

   This step binds the task view step to a task view. You can double click the task view step in order to view and edit the task view. For more information, see Drilling Down on a Task View Step.

   NOTE:  You must define the applets and view before you can perform Step 3. Otherwise, no values appear in the Task View property.

4. Define the Disable Cancel, Disable Pause, and Disable Previous properties.

   To disable a navigation button, set the disable property for the button to TRUE. For example, to disable the Cancel button, set the Disable Cancel property to TRUE.

5. Pick a Display Name, then pick a Display Name Type.

   Display Name Type controls the display of the task step of the current task pane. It is used in conjunction with the Display Name property. For more information, see Controlling the Display of Step Names.

6. Pick a Forward Button Type.

   The Forward Button Type property determines the label and type of the forward button, such as Next, Submit or Finish. If there is only one view in the task UI, then the default value is Submit. Otherwise, the default value is Next. For more information, see Validation with Forward Navigation in the Task Playbar.

7. Pick the appropriate values for the Retain Applet SearchSpec, Retain Task SearchSpec, and Retain User SearchSpec properties.

   Search specifications affect the way the state of the business component is preserved across task views. For more information, see Record Context Is Lost and Siebel Object Types Reference.

8. (Optional) Add a Task Step Context.

   The Task Step Context property defines the search specification that is used to filter data on which the view step is performed. For more information, see Defining the Context for the Step of a Task UI.

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

   The task view step does not return an output argument. However, 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 is entered by the end user through 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.

10. From the application level menu, choose the File menu, then the Save menu item.

Drilling Down on a Task View Step

After you bind the task view step to a task view, if you double click the task view step in the Task Designer, then you are navigated to the Task View UI editor, where the view that is bound to the task view step is displayed and can be edited. You can also display the run-time appearance of the view from the Task View UI editor.