Improved
- Duplicate Prevention - The setting Duplicate Prevention in Native Entry Page Lightning has been renamed to Duplicate Prevention in Entry Page, since it also applies to the Deduplicate Entry override page, and Classic is no longer supported.
Enabling this setting will block the creation of duplicate records both in Salesforce and Plauti Deduplicate Entry pages. Read more in Deduplicate Entry. - Lead Conversion - When "Contacts to Multiple Accounts" is enabled in Salesforce, you can now convert a Lead into any existing Contact and Account combination; upon conversion an indirect account-contact relationship is created.
- Matching Methods - The Date Distance in Months matching method now supports a range of up to 12 months.
- Setup - Improvements were made to the performance of the Deduplicate Setup page.
- Setup - The Setup Check now detects duplicate Deduplicate settings and duplicate Record Type scenario/match configurations, with a one-click Fix for each, grouped under a new "Org-wide checks" section. Furthermore, the Setup menu shows the number of detected setup issues, surfacing problems even before the page is opened.
- Small Trigger Footprint - The setting for enabling the Small Trigger Footprint now lets you choose between “Enable for all field updates”, and “Enable for scenario field updates”. This gives you more control over which records are queued for indexing.
Fixed
- AI Scenario Builder - Creating a scenario with the help of the AI Scenario Builder no longer fails when a field label contains special characters, such as parentheses or brackets.
- Deduplicate Entry - Lookup searches now work correctly for custom objects.
- Overall Job Results (OJR) - When using an embedded OJR overview, with the Source Record Owner filter set to "Logged-in User”, the overview now displays duplicates where the logged-in user owns at least one of the records.
- Scheduled Jobs - You can now change where existing scheduled jobs will run, e.g. from within Salesforce to on Plauti Cloud.