Siebel Business Process Framework: Task UI Guide > Customizing Task UI > Resuming a Paused Task UI >

Creating an Association That Allows the User to Resume or Transfer a Paused Task UI

This topic describes how to configure a task instance to reference a business component instance. A user can pause a task UI. The same or another user can resume the task at a later time, retaining the task state. You can configure a task to reference a business object instance so that Siebel CRM can transfer a paused task between users.

For example, assume you are a customer service representative (CSR) in a 100 person IT contact center for a computer manufacturer. The primary business process you perform, diagnosing problems with IT computer systems, beings with a task UI that requires complex information from a customer. Occasionally, the customer might call you back with diagnostic information that requires you to pause the task. Another CSR might answer the phone when the customer calls, so this CSR must access the paused task.

The CSR must look up the customer and view a list of the task UIs that are open for the CSR when the call comes in, regardless of who started or paused that task. The CSR must take ownership of the paused task and resume it. To use this pause and transfer functionality, you must associate the task with a business object instance so that Siebel CRM can retain the current task state.

To create an association to resume or transfer a paused task UI

1. Determine where you must locate the business service step in the task UI.

   For more information, see Locating the Business Service Step in the Task UI.

2. Add a business service step to the task UI using values described in the following table.

   Property	Value
   Business Service Name	Task Administration
   Business Service Method	Associate

3. Make sure the business service step you added in Step 2 is still chosen.
4. In the Multi Value Property Window, add a new input argument using values described in the following table.

   Field	Value
   Input Argument	ObjectId The ObjectId identifies the business component record that the task UI references.
   Type	Literal
   Value	Enter the RowId of the business component record that the task UI references.

5. In the Multi Value Property Window, add a new input argument using values described in the following table.

   Field	Value
   Input Argument	ObjectType The ObjectType is the name that Siebel CRM uses for the association. It uses this configuration as part of the search specification. The ObjectType is not required to match the business component name, but including it can help to keep objects synchronized.
   Type	Literal
   Value	Name of the business component that the task UI references.

6. If necessary, customize the user interface.

   For more information, see Process of Creating a View That Allows a User to Transfer a Paused Task UI.

Locating the Business Service Step in the Task UI

The task UI must call the Associate method of the Task Administration business service as early as possible in the task flow. The configuration varies depending on the following:

• The task UI creates a new record that must be associated. Siebel CRM can do this call between the view that first validates the new record and the next subsequent commit step. The user cannot view the associated record outside of the task UI before Siebel CRM saves the task transaction.
• The task UI updates an existing record. Siebel CRM must create the association with this record before it displays the first view in the task UI. In this situation, the ObjectId parameter of the Associate method typically uses the value that the Context BC Id task property contains.

Limitations of Associating a Task UI with a Long-Running Workflow Process

If a long-running workflow process creates a task UI but never starts it, then Siebel CRM cannot associate this task UI with a business object. To avoid this situation, you must configure Siebel CRM to start the task manually or automatically.