Siebel Business Process Framework: Task UI Guide > Guidelines and Techniques for Developing a Task UI > Techniques to Improve the Usability of a Task UI >

Commit Interim Data Technique

A task UI might require a long time to finish but the business requirement dictates that data that the task updated be visible to other users as soon as possible.

Using the Commit Interim Data Technique

This topic describes how to use the commit interim data technique.

To use the commit interim data technique

1. Open the Task Editor for the task UI you must modify.

   For more information, Opening the Task Editor.

2. Add a view step that reviews data that the user enters in the task.
3. At the point in the task UI where data that the user entered must become visible to other users, set the Forward Button Type property to Submit.

   For more information, see Validation with Forward Navigation in the Task Playbar.

4. Add a commit step immediately downstream of the view step you added in Step 2.

Example of the Commit Interim Data Technique

In the predefined Field Activity Main Task task UI, if the user updates the Status field, then Siebel CRM saves it to the Siebel database so that other users can view it, regardless of whether or not the task instance finishes. The following logic is involved in this example:

1. A Siebel operation step updates the activity status.
2. A task view step includes a Submit button. This task view step is immediately downstream of the Siebel operation step described in Step 1.
3. A commit step saves data to the Siebel database. This commit step is immediately downstream of the step described in Step 2.

This behavior makes sure the user understands that Siebel CRM saves the modifications, and allows the user to step back through the task UI and choose a different status before committing modifications that are visible to other users.