Success Hub
Log In

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. Apps Release 2.4.3

    2.4.3
    Production

    Improved

    • Deduplicate jobs – Better error message for jobs that fail due to an expired token, job not being found or an invalid filter value
    • Deduplicate jobs – Added a button next to failed deduplicate jobs to easily send failure logs to Plauti support

    Fixed

    • Deduplicate jobs – Incorrect total processed record count when a filter is applied only to the source value

  6. Apps Release 2.4.2

    2.4.2
    Production

    Improved

    • Deduplicate jobs – Improved job speed and reduced size consumption

    Fixed

    • Connections – Sometimes connections were not refreshed, causing them to become invalid

  7. Apps Release 2.4.1

    2.4.1
    Production

    Fixed

    • Connections – Sometimes connections failed to be added when a custom proxy was enabled

  8. Dynamics 365 Release R16

    R16, version number 1.15.0.5
    Production

    Update Instructions

    New

    This release introduces a new step for your data lifecycle management: Plauti Monitor. Monitor runs automated analyses across your Dataverse entities and fields, inside your environment. You pick the entity, the analyses, the specific fields each analysis runs against, and the thresholds. Every result displays as a meaningful indicator for your data quality: green, amber or red, not just a raw number. Then, the analysis results are stored in the Monitor Library, for a comparison over time and further analysis.

    A few examples of the different analyses available:

    • Duplicate Value Rate: the share of records sharing a value with at least one other. The number behind "I think we have a duplicate problem."
    • Value Distribution: surfaces issues such as the free-text field fragmenting into USA / US / United States, and whether it should have been a Choice field all along.
    • Hidden Choice Value Usage: how many records still use a choice field value you've hidden. Worth knowing before you delete it, because deleting a choice wipes that value from every record that had it, with no way back.
    • Field Length Utilization: flags fields where records are piling up against the character limit and getting silently truncated.
    • Future Date, Past Date Thresholds, Date Range: birth dates in 2050, records past a seven-year retention window; values outside the window you actually expect are all surfaced by these analysis types.

    Monitor runs inside Dataverse, within the security roles already present in your environment. It is included as an additional feature in your current Plauti for Dynamics installation, available after updating. Nothing new for IT to run or patch.

    Monitor is where it starts. Clean and Prevent are the rest of it, and there's more coming to Monitor itself as well.

    Improved

    • General - Page loading performance has been improved through intelligent caching of organization and environment data, resulting in faster page transitions and reduced loading times when navigating between pages.

  9. 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.

  10. 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.

  11. 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.

  12. Apps Release 2.4.0

    2.4.0
    Production

    In this release, we have added a connectivity check that verifies that the app can reach all the required URL endpoints. This check is done on startup, when adding a new connection and before starting a job.

    Update instructions, you can update Plauti Desktop and Plauti Server using the in-app upgrade feature or using the fresh-installation method. Plauti Cloud is unaffected by this change.

  13. Apps Release 2.3.2

    2.3.2
    Production

    Improved

    • Better error message in case of job errors

  14. Apps Release 2.3.0 + 2.3.1

    2.3.0
    Production

    Update Instructions

    For Plauti Server, follow the update instructions in Update Plauti Server on Windows or Update Plauti Server on Linux. Plauti Desktop can be updated with the Update button in the top right of the app. Plauti Cloud is updated by Plauti.

    Improved

    • Release for security updates
    • +2.3.1: Fix for re-connection using MS dynamics connections.

  15. Apps Release 2.2.0

    2.2.0
    Production

    Update Instructions

    For Plauti Server, follow the update instructions in Update Plauti Server on Windows or Update Plauti Server on Linux. Plauti Desktop can be updated with the Update button in the top right of the app. Plauti Cloud is updated by Plauti.

    New

    • Connections – You can now reconnect an existing connection instead of setting up a new one. This is especially useful in Plauti Server, where a consumer key and secret are configured per connection.

    Improved

    • Connections – Connections that have become invalid can now be paused.
    • Login – Clearer feedback is shown when an email address cannot be used for email login, because addresses from free email domains are not allowed.
    • Plauti Cloud – Stability and performance of jobs has been improved.
    • General – Several security improvements were made.
    • General – Diagnostics have been improved so issues can be tracked and resolved faster.

    Fixed

    • Connections – Token refresh is now retried when Salesforce responds that the request should be retried, so connections no longer drop unnecessarily.
    • Logging – Some errors were written to the log incorrectly.

  16. Apps Release 2.1.2

    2.1.2
    Production

    Update Instructions

    For Plauti Server, follow the update instructions in Update Plauti Server on Windows or Update Plauti Server on Linux. Plauti Desktop can be updated with the Update button in the top right of the app. Plauti Cloud is updated by Plauti.

    Improved

    • Patch improvement release

  17. Apps Release 2.1.1

    2.1.1
    Production

    Update Instructions

    Update Instructions for Salesforce Connections
    If you hadn't done this yet for the 2.0.1 (June 22) release:
    To connect to Salesforce Orgs, and to log in for Salesforce users, additional steps need to be taken for Plauti Cloud, Desktop and Server. These steps are mandatory.
    Please proceed here:

    Plauti Cloud: Updating Cloud for the June 22, 2026 release 

    Plauti Desktop: Updating Desktop for the June 22, 2026 release 

    Plauti Server: Updating Server for the June 22, 2026 release 

    Improved

    • Server and Desktop Upgrade - Upgrading Plauti Desktop and Plauti Server can now be done with the click of a button. In the app, use the Update button top right to update to the latest version.

    Fixed

    Scheduled Jobs - Sometimes scheduled jobs weren't started automatically.

  18. Apps Release 2.0.1

    2.0.1
    Production

    Update Instructions

    Updating the apps
    For Plauti Server, follow the update instructions in
    Update Plauti Server on Windows or
    Update Plauti Server on Linux.
    Plauti Desktop is updated automatically next time you start the app.
    Plauti Cloud is updated by Plauti.

    Additional Update Instructions for Salesforce Connections
    To connect to Salesforce Orgs, and to log in for Salesforce users, additional steps need to be taken for Plauti Cloud, Desktop and Server. These steps are mandatory.
    Please proceed here:

    Plauti Cloud: Updating Cloud for the June 22, 2026 release 

    Plauti Desktop: Updating Desktop for the June 22, 2026 release 

    Plauti Server: Updating Server for the June 22, 2026 release 

    New

    • Connections - To connect to Salesforce Orgs, an External Client App needs to be installed in each Org. This applies to all apps: Plauti Cloud, Plauti Desktop, and Plauti Server.
      Read the additional Update Instructions for this release for more information.
    • Cloud Login - Login via Salesforce is replaced by email login. Read more in the additional Update Instructions for Plauti Cloud.
    • Server Login - Login via Salesforce is replaced by email login. Furthermore, a domain restriction should be set to limit which email domains can be used. Read more in the additional Update Instructions for Plauti Server .

  19. Apps Release 1.7.0

    1.7.0
    Production

    Update Instructions

    For Plauti Server, follow the update instructions in
    Update Plauti Server on Windows or
    Update Plauti Server on Linux.
    Plauti Desktop is updated automatically next time you start the app.

    Improved

    • Plauti Desktop Connections - Reworked authentication to be compatible with the operating system configured browser.
    • Plauti Desktop - Introduced the update icon for easier upgrading to the latest version.
    • General - Several compatibility improvements have been made.

  20. 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.