General Settings

App-wide settings for Plauti Verify

Last published at: February 13th, 2026

Configure settings that apply to all of Plauti Verify in the general Settings.

Object-specific settings are configured in Object Configuration.

 

To access Plauti Verify's general Settings: 

  1. In Plauti Verify, open the Verify Setup tab.
  2. At left, click Settings.
  3. At right, click Edit to edit the settings. After configuring, click Save.

On the Settings page, you can configure the following features:

General Settings  
Verify - Default Country
 		 By default, Plauti Verify will validate input based on the default Country as defined here. 
You can change the Country value while creating or editing a record for a different country. Furthermore, users that validate for a different country often can set their own default country preference.
Verify Setup - Show API  Names Show or hide API names next to field labels. 
When toggled to Active, API names are displayed.
Verify - Disable Direct Validate Disable Direct Validate for all Objects. 
When toggled to Active, Direct Validate is disabled.
Verify - Chunk size in Direct Validate Set the chunk size for Direct Validate. Do not change this value unless advised by Plauti Support.
Verify - Disable All Record Validation Triggers

Turn off all automatic Plauti Verify trigger execution when creating or editing a record. Verifying manually is still possible.

When toggled to Active, the automatic triggers are disabled.
Verify Job - Maximum number of records per API call to DQ Server Set the maximum number of records that are forwarded per API call when validating records in batch.
Verify Job - Maximum number of records per API call when fetching results from DQ Server Set the maximum number of records that are retrieved per API call when validating records in batch.
Separate multiple address lines in the Street field by Set the delimiter for multiple address lines in Street fields, e.g. comma or line break.
Include Municipality in Addresses Include the municipality (DependentLocality) in addresses, or leave it out. 
When toggled to Active, the municipality is included.
Ensure correct order of execution when using both Direct Validate and Plauti Deduplicate's Direct Processing Only enable this setting when both Plauti Verify - Direct Validate, and Plauti Deduplicate - Direct Processing are in use. 
This setting ensures that new records are validated first, and deduplicated second, when inserted via Apex Insert/Update, API Bulk Insert, Plauti Deduplicate Apex API, or Web to Lead. This way a record is always validated and standardized, which helps in then finding a duplicate record in Direct Processing. 
When toggled to Active, this order of processing is applied.
Data Validation Server Region

Select a region for data validation. Your data will be sent to a server in the specified region for validation, and will not be transferred to any other region.
Currently this applies to Email and Phone validations. Work is in progress to have this applied to Address validations as well, but as for now no processing region can be guaranteed yet for Address validations. 

Note that this setting cannot be updated while a Verify Job is running.

 

Improved Metadata Caching  
Activate improved caching of Salesforce Metadata

Enable the improved caching of Salesforce Metadata. When toggled to Active, improved caching is enabled.

If you are not using the Plauti Verify permission set, grant your users full access to the 'rv2ObjectMeta' object to be able to use this setting.
Empty Metadata Cache
 		 Click Purge Cache to remove cached Salesforce Metadata.

Create Country State picklist cache

Only available when Salesforce's ‘State and Country/Territory Picklists' are enabled

 If you have a large number of ‘State and Country/Territory Picklists’ values (e.g. 200+ countries/territories and 1000+ states), performance of Plauti Verify can be impacted. Click Create to create a cached list of your State/Country Picklist values in order to improve performance.