Siebel Business Process Framework: Task UI Guide > Implementing Task UI > Scenario for Iterative Development of a Task UI Implementation >

Designing the Task Flow

User A now proceeds with identification of the activities within each task, as well as definition of the task flow.

For the task called Submit expense report, this yields the following activities:

1. Create expense report header.
2. Create expense items.
3. Review and submit the expense report.

Just as she did when she was drafting the business process model, User A creates this task flow using Siebel Tools. This time, however, she uses the Task Designer rather than the Process Designer. She creates the three identified activities as three separate task view steps. Because she is not familiar with the View and Applet editors, she enters only the view step names, without linking the view steps to actual task views, since at this stage they still do not exist.

The second task, Review expense report, is simple, requiring only a single task view step: Review expense report.