Identifying the Context for the Task

The business analyst must refine the task. The analyst begins by identifying the context for the task. The application developer notifies the business analyst that the submission task starts the long-running Workflow Process, so the analyst realizes that the user must manually start the submission task in a standard view. The analyst also realizes that most employees will frequently do this job task.

For these reasons, the analyst decides the development team must add the submission task to the Common Tasks task group, and concludes that the submission task does not require context passing. The context is the current record. For example, the record being submitted. The task that submits the record does not need to pass information about the submitted record to the next step in the business process.

The user must be able to frequently pause this task. For example, to provide the user a moment to find required documents. So the analyst decides that the task must use the description for the expense report as the value of the Context field in the Universal Inbox. This configuration allows the user to distinguish between different instances of the same task.

The analyst notes that Siebel CRM opens this task from the long-running Workflow Process, so the user opens it from the Universal Inbox. For this reason, the analyst does not add the review task to a task group. The review task does require that Siebel CRM pass an expense report number as an input argument. A Boolean value named Approved seems to be an appropriate output argument. The appropriate context for the Universal Inbox is a concatenation of the total amount for the expense report and the name of the submitter. For example, $450.00 from Aaron Jones.

Next, the usability analyst designs the task.