Plauti Verify release notes

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

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.

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.

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.

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

New

• Plauti Agentforce - Enhance your customer communication with Plauti Agentforce’s Verify Agent, a ready-to-use, template-based Salesforce Agent package for use in combination with Plauti Verify. The Plauti Verify Agent template provides out-of-the-box agent instructions and actions for validating email addresses and phone numbers in conversations. Customize them to fit your specific use cases. Read more here.

Improved

• General - As part of Plauti’s rebranding process, the Record Validation app is not available anymore in the App Launcher from now on. Find RV in Salesforce’s App Launcher as ‘Plauti Verify’. Don’t forget to add it to your favorites!
  Read more about the new naming in this blog, and find a list of all new names in RV and Plauti Verify old and new names.

Fixed

• Auto Process - If you try to delete an Auto Process scenario that is still in use in a Direct Validation, you are now informed of this.
• Validate Job - The Abort button was incorrectly visible at a stage of the job process where aborting the job was already not possible anymore.
• Verify Entry - Date and date/time fields are now formatted according to the user’s language setting.
• Verify Entry - Picklists work correctly again with values containing an ampersand (&).

New

• Plauti Restore - Undo Merges and other field and record changes with the new Plauti Restore solution. Keep track of changes: merges, inserts, updates and deletions, on Objects and Fields you define. Restore changes including related data to revert accidental modifications. Restore from the main Changes overview, or from a custom record tab. Read more here, or watch the video.

Improved

• Email Validation - A new Status Code has been added: 315 (Amber). This is returned when an email address is correct, but it’s being redirected or forwarded to another email address or server.
• Verify Setup - The layout of the Verify 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.

Fixed

• Address Validation - Upon validation, the status message for an address without house number now correctly states that it is verified up to Street.

Other

• Flow Actions - From Salesforce’s Winter ‘26 release onwards, flow apex actions in record-triggered flows cannot be used anymore in an immediate path (synchronous path or non-scheduled path). To prevent your flows with Plauti apex actions from failing, change the Transaction Control settings of your existing record-triggered flows to 'Always continue in current transaction’.
  Note that screen flows and auto-launched flows are not affected.
  Read more about updating your flows here.

New

• Export Data - A new Data Flow is available: Export Data. Next to importing data into your Salesforce Org, you can now export data from any Object as well. Export a CSV file with data from the entire object or a subset of records, from selected fields including parent fields. Run the Export Data Flow in Plauti Cloud, or in the new Plauti Desktop or Plauti Server apps that run on your local machine instead of in the cloud. Read more here.

Classes added

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

• rv2GenericStorageRepository
• rv2SettingsMutex
• rv2InAppNotification
• rv2InAppNotificationController
• rv2InAppNotificationRepository
• rv2InAppNotificationScheduler
• rv2InAppNotificationService

Other items added

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

• Plauti Verify Generic Storage (recordval__rv2GenericStorage__c)

Fixed

• Address Validation - For some addresses in the UK and Ireland, Plauti Verify did not return geocodes (latitude and longitude).
• Auto Processing - When creating an Auto Process job, in the job confirmation window, the actual number of records that will be processed is now displayed again, instead of the number of validations.
• Verify Entry - Rich Text Area fields now offer their rich text formatting options again.
• Verify Job - In a Verify job, at Info, on tab Selected Records, the initial number of records in the job is now displayed again, instead of the number of records left after processing.

Improved

• General - Labels have been updated to reflect the new naming. Find the settings in Verify Setup, run a job via Verify Job, etc. Read more about the new naming in this blog, and find a list of all new names in RV and Plauti Verify old and new names.
• Verify Entry (RV Entry) Tab - From Plauti Verify version Winter '26 Feature Release (2025R6) onward, the Verify Entry (RV 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 Verify Entry (RV Entry) replacement page, which will continue to exist. Read more.
• Verify Job (RV Job) - Next to Leads, you can now filter a job to run on Contacts that are in a certain Campaign as well.

Fixed

• Verify Entry (RV Entry) - Formula fields now correctly display formatted content such as images (IMAGE) or hyperlinks (HYPERLINK).
• Verify Entry (RV Entry) - In some cases, when validating a United States phone number, the country indicator erroneously switched to Canada.
• Verify Entry (RV Entry) - Multi-select picklists work correctly again with values containing an ampersand (&).
• Verify Flow (RV Flow) - In Orgs with State and Country/Territory picklists enabled, in Plauti Verify address validation flow actions, State and State Code were cleared after an otherwise successful validation.

New

• Plauti is rebranding! Record Validation has been renamed to Plauti Verify, and can be found under that name in the Salesforce App Launcher.
  For now both apps can still be used, but later this year only the new Plauti Verify app will be available.So add it to your favorites! Read More.
• RV Job - RV Job has been fully redesigned. Most changes are technical, but what you’ll notice is an improved layout for easy navigating, an option to delete old jobs in bulk, and a new job filter to run a job on Leads in a certain Campaign.

Improved

• RV Entry - The Record Type field now displays the record type name instead of its ID.

Classes added

• If you are not using the RV permission set, add the following class to the applicable profiles or permission sets:
  rv2WebJobOverviewController

Other Items added

• Add the new Plauti Verify app to your list of favorite Salesforce apps to use instead of the Record Validation app.
• If you are not using the RV permission set, assign the following app to the applicable profiles or permission sets:
  Plauti Verify (recordval__plauti_verify)
  if you currently have the Record Validation (recordval__recval_Lightning) app assigned there.
• If you are not using the RV permission set, add the following page component to the applicable profiles or permission sets:
  rv2JobOverview

Fixed

• RV Entry - If the first few digits of a phone number matched a country code, the country to use automatically changed to that country, even when there was no '+' sign in front of the number.
• RV Entry - In Person Account orgs, RV meta data such as RV Status Code or Geocode is now stored properly.
• RV Entry - Users that only have access to a -master- record type could not always save records.
• RV Entry - When copypasting a number in a number field, the last digit was omitted.

New

Plauti is rebranding! Record Validation has been renamed to Plauti Verify, and can be found under that name in the Salesforce App Launcher.
For now both apps can still be used, but later this year only the new Plauti Verify app will be available. So add it to your favorites! Read More.

Items added

• Add the new Plauti Verify app to your list of favorite Salesforce apps to use instead of the Record Validation app.
• If you are not using the RV permission set, assign the following app to the applicable profiles or permission sets:
  Plauti Verify (recordval__plauti_verify)
  if you currently have the Record Validation (recordval__recval_Lightning) app assigned there.

Improved

• General - Record Validation can now validate objects that do not have the standard Name field.

Fixed

• RV Entry - Users with Edit permission but no Create permission for an Object can edit records via RV Entry again.
• RV Entry - When removing a phone number and then clicking Undo, the deleted phone number is now properly retrieved again.

Improved

• RV Entry - Validate an existing but not yet validated address without needing to edit it first.

Fixed

• General - Making changes to a validated record after an RV field was removed or remapped will no longer result in an error upon saving.
• RV and DC - In some cases, when converting a Lead with Duplicate Check, its RV validation and metadata were not copied along.
• RV and DC - The "Target ‘Open’ button: open in a new or existing window or tab” setting is respected again when opening duplicate records found in RV Entry.
• RV Entry - When a user only has access to the - Master - record type, not to other record types of an Object, they could not save new records for that Object.

New

• Flow Actions - A new flow action has been added, "Validate All", for auto-launched flows. This flow action validates all mapped (and used) fields for a record in one go.
• Discover Data Flows, Plauti’s new import feature for Salesforce and Microsoft Dynamics. In Plauti Cloud, in the Data Importer menu, create Data Flows to process data in bulk. Import CSV or Excel files of any size into a Salesforce or Dynamics environment, with support for any Object or Entity type, and handy features like previous mapping memory. Perfect for data migration projects. Read more here.
  For now you can only insert data as new records into a Dynamics or Salesforce environment, but in the future updating, exporting and other data processing options will be available.

Classes Added

If you are not using the RV permission set, add the following class to the applicable profiles:

• rv2ValidateAllFlowAction

Fixed

• RV Entry - As used to be the case previously, Country and State picklists are available again even if they are not present on the page layout.

Improved

• Geocodes - In RV Setup, indicate per address whether geocode fields should be visible in RV Entry or not. If geocode mapping is enabled for an address, invisible geocode fields will still be updated.
• RV Entry - Dates can now be entered manually.
• RV Job - The RV Job Results page has been redesigned for a better user experience. Quickly see the validation results per record and in total, decide to save only part of a validation, and more.

Other Items Added

If you are not using the RV permission set, add the following field to the applicable profiles:

• recordval__rv2JobResult__c.recordval__RecordName__c

Fixed

• Email Validation - Email addresses that bounce because of their status ‘do not mail’ and sub-status ‘global suppression’ will now validate as Red instead of Amber.
• RV Apex API - When using Apex API to validate and save an address, it now correctly stores the status as ‘594 - Validated up to house number’.
• RV Entry - For records with a phone number country code that is shared by several countries (e.g. +1 for USA and Canada) sometimes an incorrect country flag was still shown after validating with the correct country. Existing records will show the correct flag after revalidating.
• RV Entry - For user locale settings that have a different field order for addresses (e.g. Country first instead of Street first) the address component did not work correctly.
• RV Flow Actions - Return and save geocodes in validation results.
• RV Flow Actions - When validating an address with the Address Validation flow action, the house number sometimes disappeared.

Fixed

• RV Job - In some cases RV Jobs could not be aborted.

Improved

• RV Entry - Added a number of improvements, such as better performance for fields like custom addresses.
• RV Entry - Changes made to a record in the Sales or Service Console now show up right after saving, without the need to refresh the page first.
• RV Live - Redesigned the user interface to be more user-friendly, for a better user experience. To use the new RV Live, switch out the old Record Validation page component with the new RV Live component. Try it out in your Sandbox Org! Read more here.

Classes Added

If you are not using the RV permission set, add the following class to the applicable profiles:

• plautiHttpPipeline
• plautiWebHttpRequest
• plautiWebHttpResponse
• plautiWeb, plautiWebLwcEntry
• plautiWebVfEntry
• rv2LookupController

Other Items Added

If you are not using the RV permission set, add the following Visualforce page to the applicable profiles:

• rv2KoalaHost

Fixed

• RV Setup - Users with special characters in their user name could not view RV credit and transaction information.

Classes Added

If you are not using the RV permission set, add the following class to the applicable profiles:

• rv2CustomSObjectComparator

Fixed

• RV Flows - With the State and Country picklists enabled, the State and Country fields in the RV Address flow screen component did not populate.

Improved

• RV Job - When auto-processing an RV Job, records that cannot be processed automatically will now be skipped.

Fixed

• Country/State Override - When manually re-validating a value in an RV Job result view, the State override was ignored.
• RV Entry - In some cases, when address fields are mapped to a text field and the State/Country Picklist is not used, the State code was not filled in after validation.

New

• Address Validation - RV can now add geocodes (the latitude and longitude of an address) to addresses. Read more here‍.

Improved

• RV Apex API - When validating using the RV Apex API, the validation result can now be saved. Read more here‍.

Classes Added

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

• rv2APIValidationResultv1
• rv2SaveValidationResultInputv1
• rv2SaveValidationResultOutputv1

Fixed

• RV Auto Process - After running Auto Processing on RV job results, the Results buttons were still shown.
• RV Entry - When you edited a record with RV Entry Edit, the changes you made were only visible after refreshing the page.