QUESTION:
How does DupeBlocker currently integrate with Salesforce1?
ANSWER:
Due to limitations, DupeBlocker is not supported in Salesforce1. We will continue to monitor the ability to fully support DupeBlocker in Salesforce1 as more features in the standard Salesforce platform become available in Salesforce1.
Records entered via Salesforce1 WILL trigger the DupeBlocker Scenario actions and block, warn, or auto-merge/convert records accordingly. Unfortunately Salesforce1 does not support displaying HTML error messages on standard Salesforce pages, therefore the blocking error messages ("Do Not Insert/Update" messages) are not properly formatted and will appear in plain text. As a result the "bypass block" button (if scenarios configured to allow this) will not be available either. The redirect feature is also not supported and therefore will not redirect the user to the existing record. Instead redirects will behave as a block with an unformatted error message as well.
The standard Inline Duplicates VisualForce pages (to show potential duplicates in the record detail page) are not enabled for mobile. To have this section/visualforce page displayed in Salesforce1 a custom Inline Duplicates page will need to be created. When creating the page be sure to check the "Available for Salesforce mobile apps" option in the upper right. More information on creating custom inline duplicates pages for standard objects (Accounts, Contacts, Leads) can be found here, and for non-standard/custom objects can be found here.
Salesforce1 does not support task reminder pop-ups, therefore tasks created for Warnings will not be shown immediately to the Salesforce1 user. Warnings can be viewed and deleted in Salesforce1, but the manual merge/convert functions are not compatible with Salesforce1.
Administrative functions (i.e. managing scenarios, building keys, updating settings etc.) do not work on Salesforce1. These configuration tasks will need to be managed directly in Salesforce.
