Siebel Business Process Framework: Task UI Guide > Guidelines and Techniques for Developing a Task UI > Guidelines for Developing a Task UI >

Guidelines for Organizing the Task Flow

Use the following guidelines when you organize the task flow:

• Envision a simple task UI. Envision the display of information as a series of linked pages or steps when you design a task UI. Although in many situations you can configure a task step in a single page, it is not required. If the step is complex, then you can separate it into multiple pages. Simplicity is an important design principle for a task UI.
• Simplify task complexity. Make sure the task UI is self contained and is a single point-to-point flow. During the design phase, consider the number of steps and decisions. If necessary, separate one task into multiple tasks.
• Chunk the task UI. Separate the task UI into a number of logical chunks. A task UI must guide the user through a task that is easy to follow and review. A task that is too long might disorient the user. A rule of thumb is to create chunks that include between five and seven items.
• Use the Chapter feature. You can configure task UI to use the Chapter feature to assist the user in understanding the overall job task and to monitor completion of the job task. The chapter feature provides the user with an outline of the task UI. This feature helps the user understand the work that the user already performed and how much work the user must still perform at a point in the overall task. The individual steps in a chapter can vary depending on choices that the user makes.
• Organize the task UI around logical commit points of the task transaction. For more information, see About Task Transaction.