DupeBlocker 3.10 Release Notes 

Starting in Version 3.10 (released 9/24/18) DupeBlocker is Lightning Ready!

To get started using all the new Lightning Ready features install or upgrade to the latest release.

General Requirements 

• To work properly, DupeBlocker uses various custom Lightning Components.  Salesforce requires my domain to be enabled in an organization in order to use Lightning Components.  If My Domain is not currently enabled, please follow the instructions in the Salesforce help article Set Up My Domain
• Recommended Browsers:  DupeBlocker Lightning works best in Chrome, Safari, and Firefox.  Microsoft Edge occasionally results in unexpected errors (not just with DupeBlocker components, but Lightning in general) and therefore we do not recommend DupeBlocker's use in Edge)

New Features

• No more unformatted HTML errors when a record is blocked! Also allows Bypass Block functionality and redirecting to an existing record.
  • Override the New/Edit Pages with DupeBlocker's Custom Lightning Pages
• New Lightning Component to display a DupeBlocker Potential Duplicates List directly on the Lightning Page
  • Also detects duplicates when simply VIEWING a record
• New DupeBlocker Logs tab (available in Lightning AND Classic)
  • Tracks Manual Merges/Conversions, Auto Merges/Conversions and any DupeBlocker Exception Errors
    • Can turn off exception emails by blanking out the DupeBlocker Administrator E-mail on DupeBlocker Settings
  • Note:  Classic users upgrading to 3.10 will need to manually update the DupeBlocker Application to show the new tab in the Classic UI
• Redesigned DupeBlocker Settings in Lightning
  • Same options as Classic, but a sleeker Lightning look and feel

Overriding New/Edit Pages with DupeBlocker's Custom Lightning Pages (Lightning ONLY)

Block messages, Bypass Block button and the ability to redirect to an existing record does not work on the Standard Salesforce Lightning Pages.  In order for these options to work properly the standard pages will need to be overridden with DupeBlocker Lightning custom pages.

If the Match on Insert Action is set to either "Do Not Insert" or "Redirect to Existing" in any scenarios, the New button will need to overridden for the Scenario object being checked for duplicates.  If the Match on Update Action is set to "Do Not Update" on any scenarios the Edit button will also have to be overridden for the Scenario object being checked for duplicates.

To do this go to Setup -> Objects and Fields -> Object Manager -> {Object} -> Buttons, Links and Actions

• Edit the “New” and/or “Edit” buttons (same process for both)
• Pick CRMfusionDBR101:DupeBlockerWrapper for the “Lightning Experience Override” and “Mobile Override”
• Adding a comment is optional

    
Examples:

Custom override:  Blocking message properly formatted, links to matched records, Bypass Block button shown in upper right.  If "Redirect to Existing" is the action a pop-up will be shown alerting of the redirection, then the user will be redirected to the first matching record found.



No Override, blocking message displayed on Standard Salesforce page


  
Adding DupeBlocker's Potential Duplicates List Component to Lightning Pages (Lightning ONLY)

ONLY AVAILABLE in Lightning (not in Classic), is the ability to show Warnings in a Lightning component directly on the page. This component, which can be added to the Lightning Object Pages (Accounts, Contacts, Leads and any other object enabled for deduplication), has an option to detect duplicates and create a warning (regardless of the scenario action) when VIEWING a record.  The option is enabled by default, but can be disabled if desired.

The new component is similar to the Salesforce Lightning component used to check for duplicates when Duplicate Management is enabled. We recommend removing Salesforce's component and replacing it on the Lightning page with ours.

Existing DupeBlocker customer's switching from Classic to Lightning may want to also remove the DupeBlocker Potential Duplicates related list from the object page layout, as it will be redundant when the new Lightning component is added (and the Lightning component is more robust).  Adding the related list to an object was optional in Classic so it may or may not be on the current page layout.  This can be done by selecting "Edit Object" on the Lightning page (see option in screenshot below), which takes you to Setup -> Objects and Fields -> Object Manager -> Object.  Then select Page Layout and remove it from the current related lists.

To add our component to an objects Lightning Page:

• In Lightning, access a record you want to update the Lightning Page for (i.e. An Account, Contact or Lead etc.)
• Click the tool icon in the upper right and select the “Edit Page” option

• First remove the Salesforce Duplicate Management component from the Page (will be in the “Related” area for Accounts/Contact and “Activity” area for Leads)
  • To remove, simply click the x on the component in the upper right
• Add the "DupeBlocker Potential Duplicates" custom component located on the left in the list of Lightning Components
  • Scroll to the bottom to see Custom Components
  • Drag the component to the upper right hand side of the page
• Component options will be shown on the right after adding the component
  • Check for New Dupes: When checked (default) will detect duplicates when viewing a record
    • Warnings created from simply viewing a record, will have the Triggering action “Duplicate found on View”
    • Max Number of Duplicates: Specify the maximum number of duplicates to display in the component
• Click “Save” in the upper right, then “Activation” and “Assign as Org Default”
  • To go back to the object record click “Back” and the new page with the Salesforce component removed and DupeBlocker's added will be displayed

                 

DupeBlocker Logs Tab (Lightning and Classic)

In previous releases, merges are only tracked for individual scenarios in the DupeBlocker Statistics section of the DupeBlocker Scenario object.  While this information is great for being able to view how effective in general a particular scenario is, users have requested the ability to track merges/conversions across all scenarios along with the ability to differentiate between manual vs auto merges conversions.  The new DupeBlocker Logs tab uses platform events to record these operations to a central log.

Also in previous releases, if DupeBlocker ever encountered an exception (i.e. errors building keys, unable to lock row errors, auto-merge/convert errors etc.), the error was directly emailed to the user email specified in the DupeBlocker Administrator email field in DupeBlocker Settings.  Again that feature still exists, but ALL exceptions encountered when using DupeBlocker are now also tracked in the DupeBlocker Logs.

We still recommend having the errors emailed to the DupeBlocker Admin for the immediate notification aspect, but user's can now turn off the emails by blanking our the email in DupeBlocker Settings.  If this is done and there is any unexpected behavior with DupeBlocker users are advised to manually check the DupeBlocker Log for possible errors.

Pre-built views are available also in the upper right to only show a particular Event Type.  Users can also create their own custom views. 



If storage usage for DupeBlocker Log items becomes an issue, the entries can occasionally be mass deleted.

Adding the DupeBlocker Logs tab to Classic UI

Classic users who upgrade to the new release, and will continue to use Classic vs. Lightning Experience, will need to manually add the Tab to the application.

• To do this in the Classic UI go to Setup ->  Create -> Apps -> DupeBlocker
• In the "Choose the Tabs section, locate the DupeBlocker Logs tab and add it to the Selected Tabs just after DupeBlocker Settings 

Redesigned DupeBlocker Settings (Lightning ONLY)

The settings have NOT changed (same as in Classic) but has a sleeker Lightning look and feel.



Detailed information on each Setting can be found HERE.