How You Manage Agreement Rules

An agreement rule is a collection of patterns and conditions that are defined to determine whether a merge request should be vetoed by the application or not. Merge requests that violate these rules are either automatically rejected or end in error.

An example of an Agreement Rule is CUST_CONTACT_DIFF_RESOURCE_ORG_VETO, which prevents two partner-owned contacts belonging to different resource organizations from being merged.

You can create and edit Agreement Rules in the Setup and Maintenance work area by going to the following:

• Offering: Customer Data Management

• Functional Area: Customer Hub

• Task: Manage Agreement Rules

Agreement rules let you check a merge request for any veto conditions that can prevent a merge from occurring. These rules save resources and time by obviating the task of reviewing merge requests to prevent undesired merges from being processed. Besides, agreement rules prompt you to consider alternative duplicate resolution mechanism such as linking. Note that Agreement Rules can't be set up in sandbox mode. Agreement rule can be of the following two types:

• Predefined: These are shipped out of the box with the application and are available in the predefined Agreement Rules Dictionary shipped with the application.

• User-defined: You can create your own Agreement Rules using the Manage Agreement Rules setup and maintenance task.

To know more about the two types of agreement rules see the Overview of Agreement Rules topic in the related links.