1. Business Process Framework: Task UI Guide
  2. Configuring Siebel CRM to Resolve Task Transaction Conflicts

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

The following procedure shows 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. Display the Business Component User Prop object type.

    For more information, see Displaying Object Types Used to Develop a Task.

  2. In the Object Explorer, click Business Component.

  3. In the Business Components list, locate the business component you want to modify.

  4. Expand the Business Component tree in the Object Explorer and then click Business Component User Prop.

  5. In the Business Component User Properties list, add a new record with the value shown in 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.This 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. This is 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 typically detects an update conflict or a delete conflict during a commit operation or when it receives data in the task transaction.

To configure Siebel CRM to resolve update and delete conflicts

  • Create a task property with the value shown in the following table. For more information, see Creating a Task Property.

    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.