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

Identifying Task Context

Even though she has handed over the business process definition to User B, User A still has a lot of work to do on the tasks within the process. She starts by identifying their context. Having been warned by User B that the submission task initiates the long-running workflow, she realizes that it is the end user who needs to manually start the submission task from the ad-hoc UI. She also realizes that this task is going to be frequently used by almost every employee of the company.

For these reasons, User A decides the submission task should be added to the Common Tasks task group. She also concludes that the submission task does not require any context passing. She considers that this task may, however, be frequently paused (for example, so the employee has a chance to find all required documents). Because of this pause requirement, User A decides that the task should use the expense report's description as the value of the Context field in the Universal Inbox, so as to easily distinguish between different instances of the same task.

Moving on to the review task, User A notes that is invoked from the long-running workflow, so it will be started through the Universal Inbox; for this reason, the review task does not need to be added to any task group. The review task does, however, require an expense report number to be passed as an input argument. A Boolean flag called Approved seems to User A to be a logical output argument. The appropriate context for the Universal Inbox would be a concatenation of the expense report's total amount and the submitter's name (for example, $450.00 from Aaron Jones).