Home > DupeBlocker Step by Step Instructions > Scenarios

Scenarios

Articles in this section

Default Scenarios Creating/Editing Scenarios Mapping Types Described in Detail Managing Scenario Keys

Overview

Scenarios are where the matching criteria for duplicates is defined.  Multiple scenarios can be defined for Accounts, Contacts, Leads, Lead to Contact and Lead to Account matches.  Best practice is to define a series of scenarios starting with rigid matching criteria to identify obvious duplicates, and then semi-rigid criteria to find possible duplicates.  The total number of scenarios defined is completely up to the user.

In addition to defining matching criteria, scenarios can be defined to match on just inserts or updates, or both.  Duplicates can be completely blocked with a redirect to the matching record, or configured to provide a warning for either the scenario owner or current user that a duplicate was detected.  Warnings can be reviewed, and if the records are confirmed as duplicates they can be merged or converted directly in DupeBlocker.

More information on warnings and merging and converting duplicates can be found in DupeBlocker Step by Step Instructions -> Warnings.

Scenario Filters are new in DupeBlocker 2.  Scenarios can now be customized to include filters to limit when they will be triggered.  Filters can be based on specific fields within the object itself, or based on the attributes of the current Salesforce user who is inserting or updating a record.

If you have Salesforce security configured, you have the option to enforce security settings, or bypass security when searching for duplicates.  Even if security is bypassed for identifying duplicates, security will be enforced if a user tries to merge into a record they do not have access to.

Lead, Lead to Contact and Lead to Account scenarios will work with Web to Lead inserts also, not just Leads entered directly through the Salesforce user interface.  However, Leads are NEVER blocked completely in this case, warnings are always generated instead.

More information on Web to Lead processing can be found in DupeBlocker Advanced Functions -> Web to Lead.

Although DupeBlocker is 100% customizable, there are default scenarios that ship with the application.  These should be reviewed, updated and deployed as needed.  Default scenarios are marked as undeployed when installed.  New scenarios can also be created to suit your organizations needs.

Note:  Scenarios need to be customized to work with Person Accounts to include DupeBlocker Scenario Filters and special matching criteria applies.

More information on customizing Scenarios to correctly detect Person Account duplicates can be found in DupeBlocker Advanced Functions -> Person Accounts.

There are 4 components to Scenarios: Detail, Rules, Filters and Warnings.

1.  DupeBlocker Scenario Detail:  Provides general settings for the particular scenario and DupeBlocker Statistics.

2.  DupeBlocker Scenario Rules:  Defines the matching algorithm.

3.  DupeBlocker Scenario Filters:  Define criteria as to when scenarios should be triggered based on attributes of the object or current user.

4.  DupeBlocker Scenario Warnings:  Lists all active warnings for potential duplicates detected by this scenario.

See also