Success Hub
Log In

Salesforce release notes

Scroll through to see all the exciting new features, improvements & updates we've been working on!

2026

  1. Plauti Verify Release 2026 R6

    2026 R6 (3.134)
    SalesforceProductionSandbox

    New

    • API - Validate addresses, phone numbers and email addresses in a single request with the new bulk validation API for Apex and REST. Send any combination of items, for example two addresses, a phone number and three email addresses, each under an identifier of your choice; every result comes back under the same identifier.

    Classes Added

    If you are not using the Plauti Verify permission set, add the following classes to the applicable permission sets:

    • BulkConversionService_v1
    • BulkValidationInput_v1
    • BulkValidationOutput_v1
    • PlautiBulkAPI_v1
    • PlautiBulkRestAPI_v1

  2. Plauti Context Release 2026 R6

    2026 R6 (1.6.0)
    SalesforceProductionSandbox

    New

    • Quality Scoring calculates a data quality score (1-100) for your objects, fields, and individual records, based on your analysis job results. Set which fields and checks matter most from the new Quality Score tab in Object Configuration. Download a PDF summary after each Monitor Job; this PDF report is sent to the user that started the job as well. And add the “Plauti Monitor Data Quality Score” component to record pages so your team can see a record’s score and how to improve it at a glance.

      Default weights are already set for standard objects. Configure Quality Scoring and run a Configured job to see your first data quality scores.
      Read more in Quality Score.

    Improved

    • Date Range Analysis - Configure thresholds for the Date Anomaly Rate analysis, to control the color coding of analysis results. By default, a rate of 10% or lower shows green, a rate above 10% and below 30% shows amber, and a rate of 30% or higher shows red; adjust to better reflect your situation if needed. The Date Anomaly Rate is the percentage of records with a value that are either Too Old or Too New.
    • General - To better reflect its purpose, Plauti Context has been renamed to Plauti Monitor, including feature names such as Monitor Job, Monitor Setup, etc.
    • Monitor Library - Object and Field pages in the Library have been expanded with Quality and Trend information.
    • Time Component Analysis - Since a number of date/time fields have 12:00PM (noon) as their default time, 12:00 was added to the Time Component analysis, alongside the existing 00:00 (12:00AM, midnight) check.

    Classes Added

    If you are not using the Plauti Monitor permission sets, add the following classes to the applicable permission sets:

    • Plauti Monitor Admin and Plauti Monitor End User:
      mdIRecordEvaluator, mdOnboardingConfigDeployer, mdOnboardingJobLauncher, mdRecordCountRefreshQueueable, mdLicense, mdLicenseClient, mdLicenseController, mdLicenseMapper, mdLicenseScheduler, mdBackfillIsLatestQueueable, mdBackfillThresholdsQueueable, mdDataQualityReportController, mdReportController, mdReportEmailQueueable, mdReportModelBuilder, mdReportNarrativeService, mdReportRepository, mdReportService, mdRetentionBatch, mdRetentionController, mdRetentionPurgeBatch, mdRetentionRepository, mdRetentionService, mdAggregateScoreMapper, mdRecordScoreController, mdPurgeAllFieldAnalysisResultsBatch, mdAnalysisResultHelper, mdJobFinalizeQueueable
    • Plauti Monitor Admin only:
      mdScheduledJobController, mdScheduledJobDispatcher, mdScheduledJobRepository, mdScheduledJobService, mdDefaultScoreWeights, mdOnRecordScoreWriter, mdQualityScoreCleanup, mdQualityScoreCleanupQueueable, mdQualityScoreOrphanSweepBatch, mdQualityScoreStaleCleanupBatch, mdRecordScoreRepository, mdRecordScoreService, mdRecordScoreWriter, mdRecordScorer, mdScoreCalculator, mdScoreConfigController, mdScoreConfigService, mdScoreHistory, mdScoreRecommendation, mdScoreSummary, mdScoreWeightRepository

    Other Items Added

    If you are not using the Plauti Monitor permission sets, add the following objects and fields to the applicable permission sets:

    • Custom Objects

    Plauti Monitor Admin and Plauti Monitor End User:
    MDQualityScore__c, MDLicense__c

    Plauti Monitor Admin only:
    MDRetentionPolicy__c, MDScheduledJob__c, MDScoreWeight__c

    • Fields

    Plauti Monitor Admin and Plauti Monitor End User:
    MDBatchResult__c.MergedThroughChunk__c, MDFieldMetadata__c.PreviousScore__c, MDFieldMetadata__c.ScoreHistory__c, MDFieldMetadata__c.Score__c, MDLicense__c.AnalysisSummary__c, MDLicense__c.CustomObjects__c, MDLicense__c.EditionLabel__c, MDLicense__c.FieldFilter__c, MDLicense__c.FieldInsights__c, MDLicense__c.HistoryView__c, MDLicense__c.IsSandbox__c, MDLicense__c.IsTrial__c, MDLicense__c.JobAnalysis__c, MDLicense__c.JobScheduling__c, MDLicense__c.LicenseEnd__c, MDLicense__c.OrganizationId__c, MDLicense__c.QualityScoring__c, MDLicense__c.RecordLimit__c, MDLicense__c.Refreshed__c, MDLicense__c.RetentionPolicy__c, MDLicense__c.StandardObjects__c, MDLicense__c.TrendAnalysis__c, MDObjectMetadata__c.LastConfigSavedAt__c, MDObjectMetadata__c.LastJobRunAt__c, MDObjectMetadata__c.PreviousScore__c, MDObjectMetadata__c.ScoreHistory__c, MDObjectMetadata__c.Score__c, MDObjectMetadata__c.ScoringEnabled__c, MDScheduledJob__c.Object__c

    Plauti Monitor Admin only:
    Account.QualityScore__c, Account.QualitySummary__c, Contact.QualityScore__c, Contact.QualitySummary__c, Lead.QualityScore__c, Lead.QualitySummary__c, MDFieldAnalysisResult__c.IsLatestForJobType__c, MDFieldAnalysisResult__c.PrimaryMetricValue__c, MDJob__c.IsOnboarding__c, MDJob__c.IsScheduled__c, MDObjectMetadata__c.ScoreStorage__c, MDQualityScore__c.ObjectPrefix__c, MDQualityScore__c.PreviousScore__c, MDQualityScore__c.RecordId__c, MDQualityScore__c.ScoreHistory__c, MDQualityScore__c.Score__c, MDQualityScore__c.Summary__c, MDRetentionPolicy__c.Object__c, MDRetentionPolicy__c.RetentionDays__c, MDScheduledJob__c.Day__c, MDScheduledJob__c.Enabled__c, MDScheduledJob__c.Frequency__c, MDScheduledJob__c.TimeZone__c, MDScheduledJob__c.Time__c, MDScoreWeight__c.AnalysisType__c, MDScoreWeight__c.ExternalKey__c, MDScoreWeight__c.Field__c, MDScoreWeight__c.Importance__c, MDScoreWeight__c.Object__c, Opportunity.QualityScore__c, Opportunity.QualitySummary__c

    Fixed

    • Default Value Usage - The Default Value Usage analysis now scans picklists, multi-select picklists, and combobox fields as well.
    • Past Date Threshold - In the doughnut results chart, ranges were labeled relative to today (e.g. "0-1 year ago") instead of relative to the threshold date. Labels now read "0-1 year before," etc.
    • Signal Coloring - Time Component – In some analyses, such as Time Component or Past Date Threshold, percentages in the signal column were sometimes labeled with the wrong signal color (for example red instead of green).
    • Value Distribution - Custom settings for Minimum Value Occurrences were ignored, causing jobs to always run with the default threshold of 100. Re-configure any changes you made to the Minimum Value Occurrences in order to use your settings in the analyses after the update.

  3. Plauti Assign Release 2026 R6

    2026 R6 (11.53)
    SalesforceProductionSandbox

    Update Instructions

    • In Match Rules, GREATERTHAN / LESSTHAN values are now read as exact numbers, and currency symbols or thousands separators are no longer removed. Existing Match Rules whose values contain a comma or currency symbol (for example 1,000 or $1,000) will stop matching after updating to this version. Review such rules and change the value to a plain number (1000).
    • Plauti Assign no longer allows creating an Assignee record without a linked User. If you have integrations that insert Assignee records without a User, adjust those integrations before updating, since such Assignees will now be rejected upon creation. Furthermore, update existing Assignees to have a User linked.
    • If you are updating from version 11.19 or earlier, make sure to follow the Update instructions for earlier versions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

    New

    • Assignment - Set up Processing Rules to automatically trigger assignment when a record is created with specific fields filled in, or when those fields are updated. This means triggering Assign with a Flow upon record update is not needed anymore.

    Improved

    • Assignee Summary - Frozen Salesforce users now have a "Frozen SF" status, separate from users who are inactive in Salesforce.
    • Assignees - Frozen Salesforce users can no longer be added as assignees.
    • Match Groups - Create list views for the Match Group overview. Filter records, choose which columns are visible, and save views for reuse.
    • Match Rules - GREATERTHAN and LESSTHAN operators now respect decimals and negative numbers (for example 1.9 is greater than 1.5, and -5 is less than 0) instead of truncating to whole numbers.
    • Match Rules - When a GREATERTHAN or LESSTHAN value cannot be read as a number, the routing log now explains which value (rule value, field value, or both) was not numeric.
    • Queue Order – Choose the order in which queued records are processed for each object separately. For example, process records based on a custom date/time field instead of the date they were created. When left empty, records are processed by created date and the globally set Sort Order, as before.

    Classes added

    If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin permission sets:

    • srrDynamicQueryService
    • srrFilterBuilder
    • srrListViewController
    • srrListViewRepository
    • srrListViewService
    • srrAssignmentOrderComparator
    • srrObjectConfigRepository
    • srrProcessingRuleController
    • srrProcessingRuleEvaluator
    • srrProcessingRuleOperatorService

    If you are not using the Plauti Assign permission sets, add the following class to the applicable Admin and User permission sets:

    • srrProcessingRuleLogicValidator

    Other Items added

    If you are not using the Plauti Assign permission sets, add the following Object and Fields to the applicable Admin permission sets:
    Object:

    • srrListView__c

    Fields:

    • srrListView__c.Description__c
    • srrListView__c.FilterCriteria__c
    • srrListView__c.FilterLogic__c
    • srrListView__c.ObjectType__c
    • srrListView__c.SelectedFields__c
    • srrListView__c.SortDirection__c
    • srrListView__c.SortField__c
    • srrListView__c.ViewName__c

    Fixed

    • Assignees - Assignees with an active status but no linked User were silently excluded from the assignment pool even though in Assign Setup they displayed as "Assignable." These are now shown with a "No User" status, and the queue reason names the cause.
    • Assignment - Records are no longer routed to users whose Salesforce login is frozen, in both regular assignment and SLA reassignment.
    • Assignment - Frozen users are no longer picked up as the existing owner when assigning to the owner of a matching duplicate record.
    • Match Rules - A non-numeric GREATERTHAN or LESSTHAN value no longer aborts matching with an error; instead, the rule simply does not match.
    • Reassignment - Reassignment on a missed SLA now writes to the Assignment Field configured on the Match Group instead of always writing to OwnerId. Furthermore, reassignment no longer fails on objects without an OwnerId field, such as Campaign Member.

  4. Plauti Deduplicate Release 2026 R6

    2026 R6 (3.395)
    SalesforceProductionSandbox

    New

    • Merge Rule Sets - Create multiple merge rule sets per object, so you can apply different merge logic depending on the records you merge. For example, use one merge rule set for leads with Lead Source "Web" and another for leads with Lead Source "Phone", or define separate sets per Record Type.
      Merge rule sets are available for Premium and PDM licenses.

    To determine which Merge Rule Set should be applied, add a priority and a condition, written as a Salesforce formula. When records are merged, Plauti Deduplicate evaluates the active merge rule sets in order of priority, and applies the first set whose condition is met by all records in the merge group. When no other sets match, the Default Merge Rules set is used.

    Your existing merge rules are automatically converted to the Default Merge Rules set when you update. This set is always active and cannot be renamed, deleted, or given a condition. It can be cloned to create other merge rule sets.

    Improved

    • Merge Rules - The Master Record Rule, field merge rules, and field groups have been redesigned and offer more options:

      Use the new Value based and Field based rule types. With Value based rules, the record where a field matches a specific value is selected, for example "City equals Arnhem". Field based rules can reference a different field than the field being configured.

      Add up to five merge rules per rule: a primary rule, up to three additional rules, and a date-based rule that acts as the tiebreaker. For each additional rule, choose whether it applies to the records selected by the previous rule or to all records. If the primary rule is date-based, no additional rules are needed.

    • Salesforce Winter '27 - Plauti Deduplicate has been updated for compatibility with the Salesforce Winter '27 release.

    Classes Added

    If you are not using the Plauti Deduplicate permission sets, add the following classes to the applicable Admin/User permission sets:
    dc3ControllerMergeRuleSet
    dc3MergeRuleSetMigrator
    dc3MergeRuleSetResolverBatch
    dc3MergeRuleSetSelector
    dc3MergeRuleSetValidator
    dc3MergeRuleSet

    Other Items Added

    If you are not using the Plauti Deduplicate permission sets, add the following field to the applicable Admin/User permission sets:
    dcGroup__c.AppliedMergeRuleSetId__c

  5. Plauti Assign Release 2026 R5

    2026 R5 (11.50)
    SalesforceProductionSandbox

    Update Instructions

    New

    • Match Groups - Run a Health Check on your Match Groups to find irregularities such as fields used in Match Rules that have since been deleted.
    • Permission Sets - Configure a Match Group Admin permission set to let your key users manage Match Group Settings, match rules, assignees, assignee rules, and linked capacity models/SLAs without access to org-wide Assign settings.
    • SLA - Configure Hours of Operation for an SLA so that the SLA timer only runs during the specified hours, based on the assignee's time zone.

    Improved

    • Assignees - Add working hours for all Assignees of a User in one go.
    • Assignees - When a User is deactivated in Salesforce, their Assignee records are removed, so that Match Groups only reflect active users. Note that already assigned records do not get unassigned.
    • Assignees - When creating a new Assignee, only active users can be selected.
    • Assigning - The Routing Log now captures field values for cross-object lookup rules where the matched field is on the related record.
    • Assigning - 'Update Other Fields on Assignment' now supports formulas, for example {NumberOfAssignments}+1. Any errors are logged in the Assignment Notes field.
    • Dynamic Assignees - Add Dynamic Assignees to Match Groups based on their Permission Set or Permission Set Group. This facilitates the change Salesforce is making, shifting from profiles to permission sets.
    • Dynamic Assignees - Frozen users are now excluded when resolving and counting users for dynamic assignment (inactive users were already excluded).
    • Dynamic Assignees - If for some reason the hourly scheduled job for syncing dynamic assignees has stopped running or does not exist anymore, reschedule it with the Schedule Assignee Sync Job option in Assign Setup > Jobs & Maintenance. The job will start again within the hour.
    • General - If your org's data storage is near or over its limit, a banner will warn you about this on Plauti’s Setup pages. This way it’s clear right away that any saving failures in the app are caused by a full org.
    • Match Groups - Paused Match Groups now stay active. Matched records stay queued there until the pause ends. This makes pausing different from deactivating a Match Group, where matched records are diverted instead.
    • Match Rules - Search for fields in the match rule configuration dropdown by label name or API name.
    • Match Rules - The EQUALS operator now compares numeric fields by value, so a record value of 1.0 correctly matches a rule value of 1. Text fields are unaffected and continue to match exactly.
    • Match Rules - When configuring Match Rules, cross-object fields are now clearly indicated as such so you know you can select more fields there.
    • Setup Home - The Assign Setup Home page now displays more information about your Plauti Assign configuration, such as the Global Pause Assignment status including duration, and the number of active Match Groups.

    Classes added

    If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin profiles:

    • srrFieldDescribeService
    • srrILicenseRepository
    • srrLicenseRepository
    • srrMatchRuleHealthCheckController
    • srrPackageLicenseDTO
    • srrUserPackageLicenseDTO

    If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin and User profiles:

    • srrAccessService
    • srrFormulaEvaluator
    • srrMatchRuleFieldValidator

    Other Items added

    If you are not using the Plauti Assign permission sets, add the following fields to the applicable Admin profiles:

    • MatchGroup__c.Invalid_Fields__c
    • MatchGroup__c.Last_Health_Check__c
    • SLA__c.Hours_Of_Operation_End__c
    • SLA__c.Hours_Of_Operation_Start__c

    If you are not using the Plauti Assign permission sets, add the following fields to the applicable Admin and User profiles:

    • MatchLog__c.Assignment_Notes__c

    Fixed

    • Assigning - Load Balanced Assignment now respects the configured capacity threshold again.
    • Dynamic Assignees - Reapplying the Assignee Rules now automatically re-grants licenses to eligible users again, given that licenses are available.
    • Dynamic Assignees - Synchronization no longer stops when a user's Plauti Assign license cannot be released. Assignee updates now complete as usual. Furthermore the Administrator is now notified about the affected user.
    • Dynamic Assignees - Users who already hold a license are no longer blocked from a new Match Group when your Org has run out of available licenses for Assign.
    • Error Handling - Routing and Configuration errors are now displayed in the Routing Audit Log. Furthermore, when an error notification email cannot be sent, this will not break matching anymore.
    • General - Lookup fields that are polymorphic, e.g. the content can refer to a Group or a User, are now handled correctly again when creating or editing records.
    • Match Groups - Creating and editing Match Groups now works correctly again in Education Cloud.
    • Match Groups - Custom fields are now visible and editable again.
    • Match Groups - Setting names on the Match Group Settings tab are now always displayed properly right away.
    • Metrics Dashboard - Reports no longer count Match Groups that overflowed to another Match Group as matching.

  6. Plauti Verify Release 2026 R5

    2026 R5 (3.133)
    SalesforceProductionSandbox

    Improved

    • Data Processing - When the Data Validation Server Region setting is set to US (Iowa), the full email validation flow is now kept within the US. Note that this took effect already a short while ago. Read more in Location of Plauti Data Processors.
    • Setup - Improvements were made to the performance of the Verify Setup page.
    • Transactions - In the Transactions overview, the “Time” column has been renamed to “Date”, the “Feature” colum to “Service", and the “User” column to “Source"; for consistency and to better reflect their contents.

    Fixed

    • Verify Job - A job’s address validation results now keep their “verified-with-suggestion” status (e.g. code 544) on the record until the suggestion is accepted, instead of prematurely showing the “resolved” status (594). The record, Verify Live, and the Verify Job result now all display the same status, and records with an outstanding suggestion remain flagged for action.

  7. Plauti Deduplicate Release 2026 R5

    2026 R5 (3.389)
    SalesforceProductionSandbox

    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.
    • Deduplicate Entry - Salesforce validation rules now work correctly in Deduplicate Entry when using State/Country Picklists.
    • 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.

  8. Plauti Assign Release 2026 R4

    2026 R4 (11.45)
    SalesforceProductionSandbox

    Update Instructions

    Improved

    • API - All of Plauti Assign’s triggers and Apex Classes have been updated to API version 66.0.
    • Assign Setup - Quickly switch between Setup pages of all of Plauti’s Apps, and find out more about the ones you aren't using yet.
    • Assignee Summary - When viewing ‘By User’, open the Assignee Record right from the Assignee Summary instead of first opening the Match Group.
    • Dynamic Assignees - From now on, the settings of Dynamic Assignees will not be overwritten anymore with the default Assignee Settings the next time the Dynamic Assignee Rules and Settings are applied.
    • General - Various small user interface improvements.
    • Match Groups - When cloning a Match Group, links to SLAs and Capacity Models are no longer copied along. This provides more configuration control, and prevents unintended SLA or capacity inheritance. After cloning, manually add SLAs and Capacity Models to the new Match Group if needed.
    • SLAs and Capacity Models - Cloning an SLA or Capacity Model is possible again. After cloning, the new SLA or Capacity Model is not yet linked to any Match Group.

    Classes added

    If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin profiles:

    • srrMatchGroupEvaluationRepository

    Other Items added

    If you are not using the Plauti Assign permission sets, add the following Object and Fields to the applicable Admin profiles:
    Object:

    • srrMatchGroupCandidate__c
      Fields:
    • Configuration_Values__c
    • Hash__c
    • JSONBlob__c

    Fixed

    • Assignee Rules - Currency fields can be fully used again in Assignee Rules.
    • Pause Assignment - When a Match Group is paused, incoming records are now assigned to the Queue User again, instead of staying with the creator of the record, until regular assignment is resumed.
    • SLAs and Capacity Models - Boolean fields (checkboxes) set to EQUAL TO = FALSE in SLA or Capacity Model criteria would result in an error.

  9. Plauti Deduplicate Release 2026 R4

    2026 R4 (3.384)
    SalesforceProductionSandbox

    New

    • Scenario Tester - Test a Deduplicate Scenario directly from the Scenarios setup page without running a full duplicate search. Enter two records or field values to compare, and verify that the Scenario produces the expected results. Read more here.

    Improved

    • API - All of Plauti Deduplicate’s triggers and Apex Classes have been updated to API version 66.0.
    • Deduplicate Setup - Quickly switch between Setup pages of all of Plauti’s Apps, and find out more about the ones you aren't using yet.
    • Flows - Specify which Scenarios to use in the ‘Search by ID’ and ‘Search by Field Values’ Flow Actions. When left empty, all Scenarios that are applied to Flow will be used as usual.

    Classes added

    If you are not using the PD permission set, add the following classes to the applicable profiles or permission sets:

    • dc3ControllerSetupScenarioTester

    Fixed

    • Deduplicate Convert - When converting Leads, any messages alerting the user to correctly fill out the form are now fully displayed again.
    • Deduplicate Entry - When opening Deduplicate Entry by URL Addressable, using the RecordType parameter, the default record type page layout was used instead of the specified record type.
    • Predefined Filters - Using a Date/Time parameter in a Predefined Filter would result in an error.

  10. Plauti Verify Release 2026 R4

    2026 R4 (3.131)
    SalesforceProductionSandbox

    Improved

    • API - All of Plauti Verify’s triggers and Apex Classes have been updated to API version 66.0.
    • Verify Setup - Quickly switch between Setup pages of all of Plauti’s Apps, and find out more about the ones you aren't using yet.

    Fixed

    • Address Validation - Validated (green) addresses with empty geocode fields (latitude/longitude) now get a suggestion including geocodes upon re-validation.
    • Transactions - In the Transactions Overview, filtering on Date/Time did not work correctly. This has been fixed; the filter now uses Date only.

  11. Plauti Manipulate Release 2026 R4

    2026 R4 (1.42.0)
    SalesforceProductionSandbox

    Improved

    • API - All of Plauti Manipulate’s triggers and Apex Classes have been updated to API version 66.0.
    • Manipulate Setup - Quickly switch between Setup pages of all of Plauti’s Apps, and find out more about the ones you aren't using yet.

    Fixed

    • General - Some warning messages did not contain any text.

  12. Plauti Restore Release 2026 R4

    2026 R4 (0.12.0.0)
    SalesforceProductionSandbox

    Improved

    • API - All of Plauti Restore’s triggers and Apex Classes have been updated to API version 66.0.
    • Restore Setup - Quickly switch between Setup pages of all of Plauti’s Apps, and find out more about the ones you aren't using yet.

    Classes added

    If you are not using the Plauti Restore permission sets, add the following classes to the applicable Admin and User profiles:

    • prTelemetryController

    Fixed

    • Restore Setup - A configured Object that no longer exists in the Org can now be removed properly again.

  13. Plauti Deduplicate Release 2026 R3

    2026 R3 (3.381)
    SalesforceProductionSandbox

    Bugfixes

    • Deduplicate Entry - When creating a new record from a parent record's related list, custom lookup fields now correctly pre-fill with the parent record.
    • Deduplicate Setup - Exporting a Plauti Deduplicate configuration with a large number of objects (more than ten) no longer fails due to SOQL query limits.
    • Deduplicate Setup - In Salesforce orgs with Tableau Next enabled, the Deduplicate Setup page now loads correctly. Previously, access errors related to the PersonalOrgInfo object could occur.
    • Predefined Filters - Filters on reference fields (such as CreatedById) and Record Type fields now save and work as expected.

  14. Plauti Verify Release 2026 R3

    2026 R3 (3.124)
    SalesforceProductionSandbox

    Improved

    • Verify Setup - The Transactions page now includes filtering, sorting (on the “Time” column), and pagination, to more easily search and navigate through your validation history.

    Fixed

    • Verify Entry - When clearing an email or phone field after validation, the record status now correctly reflects the remaining validated fields.
    • Verify Setup - When adding an Object, the 'Validation Field' label is now displayed correctly.

  15. Plauti Assign Release 2026 R3

    2026 R3 (11.40.2)
    SalesforceProductionSandbox

    Update Instructions

    • For all versions:
      In Salesforce Setup:
      On the Plauti Assign AssigneeRule (leadassist__AssigneeRule__c) object, add the following picklist value to the 'Operator' field:
      INCLUDES
      On the Plauti Assign MatchLog (leadassist__MatchLog__c) object, add the following picklist value to the 'Outcome' field:
      OVERFLOW
    • If you are updating from version 11.19 or earlier, make sure to follow the Update instructions for earlier versions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

    New

    • General - URLs of pages in Plauti Assign now reflect the current state in more detail, making it easier to return to specific pages. Copy the URL of a page and share or bookmark it.
    • Routing Log - The new Routing Log provides a centralized view of all assignment activities across your organization. View the Routing Log overview from the Assign Routing Log tab, or access routing history on each Match Group. Click a record name to view extensive log information.
      This first iteration starts with the basics; in following releases more features will be added.
      Note that the Routing Log tab only displays routing information from the time of update onward. Earlier info is still available on the MatchLogs tab.

    Improved

    • Assignees - Update working hours across multiple Match Groups in bulk. This is particularly useful if your users are Assignees in several Match Groups.
    • Assignees - On the Assignee Summary tab, activate or deactivate Assignees across multiple Match Groups in one go.
    • Assignees - The last Assignee features, such as availability statuses "Out of Office" and "Calendar Busy", and the Working Hours select list to quickly set a different working hour schedule for an Assignee, have been moved to the Assignee Summary tab.
    • Dynamic Assignee Rules - A new ‘Includes’ operator is available for matching users based on values within multi-select picklist fields. Note that when inverted, so “NOT Includes”, it does not find empty values.
      To use this operator, first add it to the 'Operator' field on the Plauti Assign AssigneeRule object. See the Update Instructions above.
    • SLA Reassignment - Prevent records from being reassigned to a user who previously missed the SLA for the record, improving accountability and response times. Skip only the initial Assignee or all previous Assignees.
    • SLA Reassignment - Set a limit on how many times a record is reassigned when an SLA is missed. Assign records that reached the reassignment limit to a specified ‘SLA User’, or apply the Routing Plugin to decide the next course of action; see below.
    • SLA-based Actions - The Routing Plugin can now react when a record reaches its SLA reassignment limit. Use the ‘ASSIGNMENTSLAMAXREASSIGNMENT’ plugin action for example to assign a record to a different Match Group after a certain number of reassignments. Read more here.

    Items added

    If you are not using the Plauti Assign permission sets, add access to the following Tab to the applicable Admin profiles:

    • Assign Routing Log

    Fixed

    • Dynamic Assignee Rules - Boolean fields are handled correctly again when configuring dynamic assignee rules.
    • Match Rules - Text Areas (255 characters) can be used again when configuring Match Rules.

  16. Plauti Restore Release 2026 R3

    2026 R3 (0.10.0.0)
    SalesforceProductionSandbox

    New

    • Change Details - A Change Information modal was added with more record, merge, and restore details. In the Restore Changes overview, click a change’s name to access it.
    • Restore Audit - Restores are not removed from the Restore Changes overview anymore, giving you a permanent audit trail for every rollback. Changes that were logged but not restored are still removed according to your retention settings.

    Improved

    • Changes Overview - Merge changes are grouped in Multi Merges to clearly display the master record together with its merged loser records. Click ‘Restore’ at the master record to restore all loser records together in one go.
    • Changes Overview - Restores now display a restore status (Success, Partial, Failed) after a restore operation completes. This helps identify issues that require manual attention.
    • Object Configuration - When configuring objects for tracking, you are warned if Track Updates or Track Merge is enabled without any fields or related objects configured.
      Furthermore, the Tracked Related Objects overview now includes a Priority column, to make it clear which related objects will be restored first. In large or complex orgs not all related records might be restored due to Salesforce governor limits. Read more here.
    • Restore Setup - View the storage usage of tracked changes, broken down by change type (Insert, Update, Delete, Merge) in a chart displayed on the Setup Home dashboard.

    Fixed

    • Restore Merge - In some cases, related records were not restored correctly after restoring a merge.
    • Restore Setup - Deployment failures now display the correct error message.

  17. Plauti Deduplicate Release 2026 R2

    2026 R2 (3.379)
    SalesforceProductionSandbox

    New

    • AI Merge Recommendation - Use AI-powered field selection for Auto Merge and Direct Processing, in combination with the merge rules for non-AI fields.
    • Plauti Apps – Deduplicate your records even before importing them into your org with the Import Records data flow in Plauti Desktop, Server and Cloud (previously DC Local). Duplicates will not be imported, keeping your Salesforce org clean.
    • Scenarios – Not sure how to set up an efficient scenario for finding duplicates? Use the new AI Scenario Builder to come up with scenarios that suit your needs. Based on the object fields you are using, this AI Assistant will ask targeted questions to understand how you want to compare records. It generates a scenario proposal that you can refine through follow‑up questions. Once you’re satisfied, save and deploy the new scenario. Read more here.

    Improved

    • Audit Logs - When fields are merged based on AI Merge Recommendation, the Audit Logs record that field value selection was based on AI Recommendation, as well as the AI’s reasoning for its decision.
    • Deduplicate Setup – The layout of the Deduplicate Setup pages has been improved with an intuitive user interface. To prevent accidental edits to settings, all changes to the setup now need to be confirmed by clicking 'Save'.
      Non-System Administrators now need the Salesforce system permission ‘Customize Application’ to edit all settings in Deduplicate Setup, instead of just the General Settings.
    • PD REST API – Specify which deduplicate scenarios to use during REST API deduplicate search operations. Read more in the Plauti SDK library.
    • Plauti Desktop/Server: A number of improvements were made. Jobs will now continue running when your machine enters sleep mode, you can disable SSL certificate checks or enable TLS, and more. Read more in the Plauti Apps release notes.
    • DC Entry Tab – From Plauti Deduplicate release 2026 R1 onward, the DC Entry tab that can be added to the Salesforce Navigation Bar will no longer be supported. Note that this is not the same as the Deduplicate Entry (DC Entry) replacement page, which will continue to exist. Read more here.

    Classes added

    If you are not using the PD permission set, add the following classes to the applicable profiles or permission sets:

    • dc3ConverseWithAiJarvis
    • dc3ConverseWithAiTypes
    • dc3HierarchyBatch
    • dc3IConverseWithAi
    • dc3ObjectConfigMigrator
    • dc3ObjectConfigRepository
    • dc3ScenarioBuilder

    Bugfixes

    • NPSP Insert Prevention - In NPSP Orgs, in some cases, duplicate prevention in native entry pages (Lightning) did not work.
    • Manual Merge - Time fields can be edited again in the ‘Preview’ column, thus overriding the field preselection.
    • PD Merge – In some cases, Plauti Restore would interfere with Plauti Deduplicate Manual Merge activities.

  18. Plauti Verify Release 2026 R2

    2026 R2 (3.123)
    SalesforceProductionSandbox

    Improved

    • Address Validation - Choose to include the municipality (DependentLocality) in addresses, or leave it out, with the new ‘Include Municipality in Addresses’ setting.

    Fixed

    • State/Country Codes - Verify Live can handle State and Country Codes again when they are stored in text fields.
    • Verify Entry - Address suggestions respect the Verify Settings option ‘Separate multiple address lines in the Street field by’ again when set to “Line Break”.

  19. Plauti Assign Release 2026 R2

    2026 R2 (11.34)
    SalesforceProductionSandbox

    Update Instructions

    If you are updating from version 11.19 or earlier, make sure to follow the Post-Update instructions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

    Fixed

    • Capacity Models – In some cases, newly added criteria in Capacity Models were displayed in an unexpected order.

  20. Plauti Restore Release 2026 R2

    2026 R2 (0.8.0.0)
    SalesforceProductionSandbox

    Update Instructions

    If you are currently tracking merges, make sure to configure which related Objects are tracked. Without any related Objects configured, no related Objects will be restored when restoring a merge.
    Take care to configure this as soon as possible after your Org was updated to this version, particularly when automated merging processes are in place. Watch this video for an extensive explanation, or read more here.

    New

    • Merge Tracking - Configure which related Objects are tracked during merges. For records with a large number of related Objects, or a few complex relations, this ensures the most important related Objects get priority upon restore. Without this setting configured, related Objects will not be tracked for recovery anymore.
      If you are currently already tracking merges, and want to be able to restore related Objects, make sure to configure this setting! Read more here.

    Improved

    • Restoring - Restore multiple changes at once. Select up to 20 changes from a change list view to undo in one go.

    Classes added

    If you are not using the Plauti Restore permission sets, add the following classes to the applicable Admin profiles:

    • prSObjectService

    Fixed

    • Permissions - Non-admin users that do have one or both of the Plauti Restore permission sets can now merge records again with merge tracking enabled.