Siebel Business Process Framework: Task UI Guide > User Interface Elements of Siebel Task UI >

About the Task View

This topic describes the task view. It includes the following topics:

• Task Applet
• Task Playbar Applet
• Radio Button Group
• Applet Message

A task view is a type of view that can include both standard applets and task applets that provide the end user a way to view application data on which the task UI is working, and to allow user input. The task view contains a playbar applet that includes buttons, such as Next and Previous, that allows the user to proceed through the task in a stepwise, guided fashion. A task view can include optional elements to enhance usability, such as a radio button group or applet message. The task view itself is a required element. To view an example of a task view, see Figure 8.

For more information, see:

• Defining a Task View Step
• Process of Defining a Task View
• Guidelines for Designing a Task View

Templates That Are Used with a Task View

When you define a task view, you use a standard web template that is modified with the IsInTask clause. The template controls behavior that is specific to a task view. The web template of a task UI does not display the applet title, applet menu, screen menu, thread applet, thread field, or thread title. Each task view includes a title in the top left corner, indicating to the end user that the view is not a standard view.

A task UI does not require a specialized task view template. However, the following templates are typically used for a task view:

• View Detail (Parent with Pointer)

  You can use this template for your base task view. This template allows you to customize your task UI, and place applets side-by-side in order to provide the end user a more structured view.

• View 1 Over 2 Over 1

Style Sheet of a Task UI

You use the main_task.css style sheet in order to define the look and feel of a task UI. If you modify the style sheet for a task, then the changes apply globally to all your tasks.