Now that DupeBlocker has been installed and configured, end users need to be notified of the changes that will be seen in Salesforce as the objects you implemented DupeBlocker for are inserted or updated.
In an effort to facilitate user adoption of this new software, a sample introduction letter has been developed that can be customized based on the specific configuration choices, and ultimately sent to the Salesforce end users.
The Sample Introduction Letter can be found HERE.
Things to consider when customizing the letter:
- Will Tasks be generated for Warnings?
- If so, who will the Tasks be assigned to: Scenario Owner or Current User or both?
- Private or public sharing model?
- If private, is Bypass Security checked?
- Note: If Bypass Security is checked (private org) it is recommended that Warning Tasks be assigned to the Scenario Owner as the user may not be able to merge potential duplicates based on their specific sharing rules.
- Will duplicates be blocked, redirected or just reported?
- Will the action vary by scenario?
- Did you choose to add the DupeBlocker Potential Duplicates related list to the objects
- Did you choose to add the DupeBlocker Inline Duplicates List to the object records
- Will users be allowed to delete Warnings?
- If yes, ensure they have delete permission on the DupeBlocker Warning Object
- Will users be allowed to merge/convert duplicates?
- If yes, ensure they have the appropriate permissions in Salesforce to merge records
- Note: If a Warning is generated and the user does not wish to merge/convert the potential duplicates, only the DupeBlocker Administrator will be able to delete the Warning. 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 this can be done based on the specific profile, this option could be enabled for managers but not for general users.