What to expect in the summer release (our rebranding journey)
In our Winter release, we announced Plauti’s rebranding and began rolling out changes to our solutions. We’re excited to share that, with our upcoming Summer release, we will take the next step in this journey by extending the new Plauti branding even further, bringing more clarity and consistency across your Plauti experience.
What’s changing?
In this release, we’re updating all visual elements in our apps to reflect the new branding. This means that labels and display names for components, objects, fields, permission sets, custom settings, flow actions, and more will be renamed to align with Plauti’s refreshed solution and platform branding.
Rest assured: This update is visual only.
We have not changed any API names or technical identifiers behind the scenes. Your current configurations, automation, and integrations will continue to work exactly as before, with no impact or required changes from your end.
Updated solution names
As a reminder, here are the new names for our key solutions:- Record Validation → Plauti Verify
- Duplicate Check → Plauti Deduplicate
- Data Action Platform → Plauti Manipulate
- Super Round Robin → Plauti Assign
- Plauti Data Orchestration → Plauti Orchestrate
Updated solution names
As a reminder, here are the new names for our key solutions:
- Record Validation → Plauti Verify
- Duplicate Check → Plauti Deduplicate
- Data Action Platform → Plauti Manipulate
- Super Round Robin → Plauti Assign
- Plauti Data Orchestration → Plauti Orchestrate
What has been renamed?
Here’s a summary of the changes you’ll see in the Summer release:Components
- DC Job → Deduplicate Job
- DC Setup → Deduplicate Setup
- RV Job → Verify Job
- RV Setup → Verify Setup
Objects
- Duplicate Check Log → Plauti Deduplicate Log
- DAP Audit Log → Plauti Manipulate Audit Log
Fields on objects
- RV Record Status → Verify Record Status
- RV - Validate Phone Number → Plauti Verify - Validate Phone Number
- Duplicate Check Index → Deduplicate Index
- Use Round Robin → Use Assign
Permission sets
- SRR Admin → Plauti Assign Admin
- Duplicate Check for Salesforce → Plauti Deduplicate
- Record Validation for Salesforce → Plauti Verify
Custom settings
- DC Trigger Management → Deduplicate Trigger Management
- Record Validation Default Country → Verify - Default Country
Flow actions
- RV - Validate Address (screen) → Plauti Verify - Validate Address (screen)
- DC - Find Duplicate by Record ID → Deduplicate - Find Duplicate by Record ID
Additional components
- Record Validation Address Input → Plauti Verify Address Input
- DAP Actions → Manipulate Actions
Custom metadata types
- SRR Queue Processor Batch Size → Assign Queue Processor Batch Size
What has been renamed?
Here’s a summary of the changes you’ll see in the Summer release:
Components
- DC Job → Deduplicate Job
- DC Setup → Deduplicate Setup
- RV Job → Verify Job
- RV Setup → Verify Setup
Objects
- Duplicate Check Log → Plauti Deduplicate Log
- DAP Audit Log → Plauti Manipulate Audit Log
Fields on objects
- RV Record Status → Verify Record Status
- RV - Validate Phone Number → Plauti Verify - Validate Phone Number
- Duplicate Check Index → Deduplicate Index
- Use Round Robin → Use Assign
Permission sets
- SRR Admin → Plauti Assign Admin
- Duplicate Check for Salesforce → Plauti Deduplicate
- Record Validation for Salesforce → Plauti Verify
Custom settings
- DC Trigger Management → Deduplicate Trigger Management
- Record Validation Default Country → Verify - Default Country
Flow actions
- RV - Validate Address (screen) → Plauti Verify - Validate Address (screen)
- DC - Find Duplicate by Record ID → Deduplicate - Find Duplicate by Record ID
Additional components
- Record Validation Address Input → Plauti Verify Address Input
- DAP Actions → Manipulate Actions
Custom metadata types
- SRR Queue Processor Batch Size → Assign Queue Processor Batch Size
A complete overview of all changes per app can be found at our support page: https://www.plauti.com/support
Please note: These updates apply solely to visual labels. API names, field references, and all technical backend identifiers remain unchanged and stable.
Why we’re making these changes
Our rebranding is about more than just new names—it’s about delivering a clearer, more integrated experience across our platform. With these updates, navigating Plauti and understanding feature sets will become easier, especially as we continue to add new capabilities in the future.
What do you need to do?
Nothing! All changes are applied automatically. There is no required action from your side. Your integrations, automations, and customizations will continue to function as expected.
If you have any questions about these updates or need help locating a rebranded feature in the UI, our support team is always happy to assist.
