1. Business Process Framework: Task UI Guide
  2. Task Chapter

Task Chapter

A task chapter is a list of steps that reside in a task that Siebel CRM groups under a common chapter name. A task chapter is an optional UI element that provides a map of what lies ahead in completing the task, and what work has been finished in the task. Use the task chapter to configure a logical grouping of task steps. You can display the chapter name with the names of task views in the current task pane.

If a task chapter is defined when a user first opens a task, then only the chapter name appears in the task pane. If Siebel CRM runs the first task view step of a chapter, then it expands the chapter name in the task pane. It does this to display the names of task views that the user finished. In the current chapter, the task pane displays view steps that the user visited in the order of visitation. The current view step appears in bold.

If you assign one step to a chapter, then you must assign all other steps in the task to a chapter. Although you can create many chapters for a task, it is recommended that you only create as many chapters as is required.

The image in Current Task Pane displays a task named Create New Account that includes two chapters. The chapter name provides details for the following parts of the task:

  • Enter New Account

  • Enter New SR

The example (in Current Task Pane) illustrates that the user is currently performing the Enter Account Details step.

For more information, see Creating a Task Chapter.

Using Color with a Task Chapter

You can use color in the Task Editor to differentiate between chapters. Steps that share the same color reside in the same chapter. Each chapter includes a Color property in the Multi Value Property Window (MVPW) pane where you define a chapter.

Using Chapters with a Subtask

You can use the Task Editor to assign a task step to a chapter for a parent task but not for a subtask. If you assign a chapter to a subtask step, then Siebel CRM groups the steps that reside in the subtask under the same chapter header of the subtask step. It does this when it runs the subtask.