Overview
DupeBlocker is fully customizeable to meet the needs of almost any organization. Although it can be implemented with a few easy steps, it is recommended that users review their specific business needs prior to implementation and customize Salesforce, DupeBlocker Settings and the supplied matching scenarios accordingly.
Quick Start Guide
DupeBlocker Classic can be implemented in 3 easy steps:
1. Go to the DupeBlocker Settings tab to load the default scenarios and review the default settings, making changes as necessary.
-
- The DupeBlocker Settings allow for customizing various matching options, enabling non-standard objects for matching (e.g. Opportunities, Assets, custom objects etc.), and configuring other key features.
- More information on customizing the DupeBlocker Settings can be found HERE.
- Note: The DupeBlocker Settings tab needs to be accessed to load the default settings and begin duplicate detection. Even if no customizations will be done to the supplied settings, this tab still needs to be accessed to complete the initialization of DupeBlocker.
2. Go to the DupeBlocker Scenarios tab and review the default deduplication scenarios. Update, deploy and/or create new scenarios to suit your organizations needs.
-
- DupeBlocker ships with two standard matching scenarios for Accounts, Contacts, Leads and Lead to Account and Lead to Contact matching. These can be used as is, customized and/or deleted to accommodate your specific needs.
3. Rebuild the scenario keys for all deployed (activated) scenarios. This is done by opening a scenario and clicking Rebuild All Keys.
A customization checklist can be found HERE .
DupeBlocker Settings
Options are available for customizing the application as a whole and/or customizing various mapping types to maximize finding duplicates. DupeBlocker comes with default settings and can be implemented without customization, however this tab must be selected after install to create a DupeBlocker license, and load the default scenarios and settings. Settings can be updated at any time.
Settings available for customization include:
- General Settings: Options for customizing the application as a whole
- DupeBlocker Administrator email
- Key building options
- Options to create Warnings when bypassing a block, disable Task pop-up reminders, and disable all DupeBlocker functionality
- Specify DupeBlocker activity tracking fields
- Enable Objects: Allows for duplicate detection for objects other than Accounts, Contacts and Leads
- e.g. Opportunities, Assets, custom objects etc.
- Scenarios CANNOT be created for other objects until they have been enabled
- Clean Account Name Settings: Rules for matching similar Account names when using the Cleaned Account Name mapping type (common punctuation to ignore or standardize, common suffixes and prefixes to ignore).
- First Name Mappings: Used with the FirstName mapping type to match a nickname to its full equivalent, e.g. Mike will match to Michael.
- State Mappings: Used with the State Match mapping type to match a US or Canadian state abbreviation to its full name
- Country Mappings: Used with the Country Match mapping type to match 2 digit, 3 digit, and full country names (uses ISO codes)
- Web Lead Sources: Specify the Lead Sources that are assigned to Web to Lead inserts. Ensures that Leads entered via Web to Lead will NEVER be blocked entirely.
- More information on Web to Lead can be found HERE.
More information on Mapping Types can be found HERE.
Detailed information on DupeBlocker Settings can be found HERE.
Deploying Scenarios
DupeBlocker ships with two standard matching scenarios for Accounts, Contacts, Leads and Lead to Account and Lead to Contact matching. No default scenarios are provided for non-standard objects, these will need to be built after enabling the object for duplicate detection in the DupeBlocker Settings.
Before using DupeBlocker these default scenarios 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. Scenario keys will need to be built for all deployed scenarios before they can be used.
Details regarding the default scenarios that ship with DupeBlocker can be found HERE.
More information on creating/customizing scenarios can be found HERE.
Building Scenario Keys
Once all scenarios are in place and deployed, duplicate keys will need to be built so that duplicates can be identified. Before building keys refer to the System Requirements help page for information on Salesforce storage requirements needed.
Instructions on how to build and maintain keys can be found HERE.
Additional Steps To Ensure Users Have Proper Access to the DupeBlocker Objects
Customizing Profiles
To access user profiles go to Setup->Administration Setup->Manage Users->Profiles.
Enabling Apex Class Access
Note: This step is NOT required if the instructions were followed during installation/upgrade to Install for Specific Profiles -> Set Access Level for all profiles -> Non-admin Users _>Set .
To verify this go to Setup->Develop->Apex Classes page and click on the Security link next to DB_WebServices and confirm that all profiles are enabled. Add additional profiles as necessary.
If any custom Apex Classes were created to customize redirects or Inline Duplicate Lists, these will also need to be added to the profiles.
Adding Visualforce Pages to User Profiles
Note: This step is NOT required if the instructions were followed during installation/upgrade to Install for Specific Profiles -> Set Access Level for all profiles -> Non-admin Users _>Set .
All user profiles should have access to these Visualforce pages (at the bottom of the profile settings):
- CRMfusionDBR101.DB_Account_Inline_Duplicates_List
- CRMfusionDBR101.DB_Contact_Inline_Duplicates_List
- CRMfusionDBR101.DB_Help
- CRMfusionDBR101.DB_Lead_Inline_Duplicates_List
- CRMfusionDBR101.DB_Match_Redirector
- CRMfusionDBR101.DB_Scenario_View
- CRMfusionDBR101.DB_Warning_Convert
- CRMfusionDBR101.DB_Warning_Merge
Any DupeBlocker Administrator profiles should have access to ALL DupeBlocker Visualforce pages (full System Administrator profiles will already have the new profiles added). Not updating the profiles with access to these pages will result in "Insufficient Privileges" message when the user attempts to merge/convert duplicates, or when an attempt is made to Redirect to Existing record per the Match on Insert Action:
Non-Admin Profiles should look like this after the new pages have been added:
If any custom Visualforce pages were created to customize redirects or Inline Duplicate Lists, these will also need to be added to the profiles.
Updating Field/Object Permissions for the DupeBlocker Custom Objects
All standard Salesforce profiles will not have access to the DupeBlocker custom objects and CANNOT be updated to gain access. In order for users to have access to the DupeBlocker objects they will need to be assigned a custom profile.
Note: This step is NOT required if the instructions were followed during installation/upgrade to Install for Specific Profiles -> Set Access Level for all profiles -> Non-admin Users _>Set .
Existing custom profiles will need to be updated "Read" only access to the following DupeBlocker Objects, and all fields on the same objects should be visible and editable for all custom profiles.
- Warnings
- Potential Duplicates
- Scenarios
- Filters
- Target Filters
- Rules
All non-admin custom profiles added after the installation of DupeBlocker should be updated to have read access to the same DupeBlocker objects listed above, and all fields on those objects should be visible and editable (where possible).
By default, non-admin users will not be able to manually delete a warning since they have "Read" only access to this object. Access can be granted to users to delete warnings, but this could defeat the purpose of DupeBlocker (user chooses to ignore the warning, but the record is in fact a duplicate and should be merged/converted). Since object permissions can be updated at the profile level, this option could be enabled for managers but not for general users.
System Administrators always have full access, so they can delete warnings also.
Optional Steps to Improve Duplicate Visibility Directly on Object Pages
Customizing Page Layouts
Page layouts can be updated to show an inline list of potential duplicates in the detail section (where object fields are displayed). The DupeBlocker Potential Duplicates related list can also be added to the Account, Contact and Lead page layouts. These customizations are optional as some customers prefer have DupeBlocker "run in the background" without users being aware of duplicates being detected.
Note: The Inline Duplicate List is available for ANY object whereas the DupeBlocker Related List is ONLY available for Accounts, Contact and Leads.
If you choose to update the page layouts, this can be done in Salesforce by going to Setup->Customize->{Object Name}->Page Layouts.
Inline Duplicate List
The list of potential duplicates can be displayed within the actual record itself by creating a new section and adding a supplied Visualforce page.
- Visualforce Pages supplied for Leads, Contacts, Account
- DupeBlocker - Lead - Inline Duplicates List
- DupeBlocker - Contact - Inline Duplicates List
- DupeBlocker - Account - Inline Duplicates List
- Custom Visualforce Pages will need to be created if wanting to:
- Modify the fields displayed for Leads, Contacts or Accounts
- Display duplicates for non standard objects
- Instructions and sample code can be found in the following 2 Validity Community Solutions
Instructions to add the desired Visualforce page to the Page Layout
1. Select the Page Layout for the desired object
2. Under Fields select Section and drag to the
desired location on the page layout
3. Create a 1-column section and name it "DupeBlocker Potential
Duplicates List" (or similar) and click OK
4. Select Visualforce Pages and drag the
"DupeBlocker - {object} - Inline Duplicates List"
page to the new section
Click the blue area to show the tool icon, , select Show Scrollbars option, save the page layout.
Related List: DupeBlocker Potential Duplicates
Updating the related lists on Accounts, Contacts, and Leads.
It is also recommended that the Related List Layout be updated to include the duplicate warning and scenario that triggered the warning. This will allow the user to go directly to the warning and ultimately convert/merge the potential duplicates. To do this, while still in edit mode, click on the tool icon for the DupeBlocker Potential Duplicates related list that was just added. Select Duplicate Warning and Scenario from Available Fields on the left and add to Selected Fields. Also, uncheck the New box under standard buttons.
More information on DupeBlocker Potential Duplicates can be found HERE.
Click HERE for information on configuring DupeBlocker for Lightning.
