Siebel Business Process Framework: Task UI Guide > Testing, Troubleshooting, Deploying, and Administering a Task UI > Administering a Task UI >

Configuring Siebel CRM to Resolve Task Transaction Conflicts

This topic describes how to configure Siebel CRM to resolve task transaction conflicts. For more information, see About Task Transaction.

Configuring Siebel CRM to Resolve Duplicate Conflicts

This topic describes how to configure Siebel CRM to resolve duplicate conflicts. A duplicate conflict is a type of conflict that occurs when a unique key violation exists in the RDBMS during a commit.

To configure Siebel CRM to resolve duplicate conflicts

1. Open Siebel Tools.
2. Display the Business Component User Property object type.

   For more information, see Displaying Object Types You Use to Develop a Task UI.

3. In the Object Explorer, click Business Component.
4. In the Business Components list, locate the business component you must modify.
5. In the Object Explorer, expand the Business Component tree, and then click Business Component User Prop.
6. In the Business Component User Properties list, add a new record using values from the following table.

   Name	Description
   Dup Conflict In Task	Enter one of the following values: Resolve. Siebel CRM writes the duplicate record with the Conflict Id field set to the value of Id, by default. Fail. Siebel CRM stops the task transaction. Ignore new record. Siebel CRM skips the duplicate record but saves the rest of the task transaction.

Configuring Siebel CRM to Resolve Update and Delete Conflicts

You can configure Siebel CRM to resolve the following types of conflicts:

• Update conflict. Occurs if Siebel CRM modifies the same record inside and outside of the task transaction. Similar to the standard UI, Siebel CRM detects the update conflict according to the Modification Id system field.
• Delete conflict. Caused by one of the following reasons:
  • Siebel CRM deletes a record in a task transaction, and then updates this record outside the task transaction.
  • Siebel CRM updates a record in a task transaction, and then deletes this record outside the task transaction.

Siebel CRM detects an update conflict or a delete conflict in the following situations:

• When it gets data in the task transaction
• During a commit

To configure Siebel CRM to resolve update and delete conflicts

• Create a task property using values from the following table.

  Property

  Description

  On Conflict

  Use one of the following values: Continue operation. Siebel CRM overwrites modifications that the user saves outside of the task transaction with modifications that the user makes in the task transaction. If the user deletes the record outside of the task transaction, then Siebel CRM returns an error message. Cancel operation. Siebel CRM displays an error message that describes the conflict. Data that resides in conflicting fields in the task transaction are lost. The user must manually reenter values in the fields to resolve this conflict.

  For more information, Creating a Task Property.