Clone Masking Rules to Objects User Guide
AutoRABIT Vault User Guide
This guide explains how to clone existing masking rules to fields on one or more destination objects, review the rules that Vault will create, start the cloning operation, and monitor or retry the resulting bulk clone jobs.
How rule consolidation works
Vault creates cloned rules by destination object and compatible field type. Within a destination object, selected fields with the same field type are combined under one cloned rule. The resulting rule retains the masking style and masking value of the selected source rule.
Observed selection
Result
Interpretation
6 picklist fields on AccountTeamMember
1 rule masks 6 fields
All six fields share the picklist type and are combined into one rule.
133 fields across 5 destination objects
12 rules mask 133 fields
Vault counts each distinct compatible field type within each destination object as a separate cloned rule.
Before you begin
Confirm that the required source masking rules exist in the selected Salesforce org.
Identify the destination objects and fields to which the rules must be cloned.
Ensure each destination field has the same field type as the selected source rule.
Review fields marked as already having masking configured; these fields are not available for a new cloned assignment in the observed flow.
Open the clone workflow
Select source masking rules
The Select Rules step lists available masking rules from the selected source org.
Add destination objects
The Destination Objects step is used to select target objects and configure compatible fields for each object.
Select compatible destination fields
Select each destination object tab and choose the fields that must receive the cloned rule. Vault applies a source rule only to destination fields of the same field type and displays a clone preview for the active object.
Understand the object-level readiness summary
For AccountTeamMember, all six selected fields are picklist fields. Because they share the same compatible field type, Vault groups them under one cloned substitution rule.

Six selected picklist fields on AccountTeamMember

One cloned rule configured to mask six AccountTeamMember fields
Displayed summary: Ready to clone: 1 rule will be created, masking 6 fields on AccountTeamMember.
Review the complete clone summary
Select Continue to open Summary. Review the source org, selected masking rules, destination objects, field-to-rule mappings, masking styles, source objects, and clone eligibility before starting the operation.
Displayed summary: Ready to clone: 12 rules will be created, masking 133 fields across 5 objects.
Start and monitor the clone operation
After Clone is selected, Vault confirms that the operation was initiated and directs the user to Masking > Bulk Clone Rules. A separate job is created for each destination object.

Clone operation initiated successfully

Bulk clone jobs created for the destination objects

Bulk Clone Rules list with destination-specific jobs

Job statuses and actions

Available action for an unsuccessful bulk clone job
Retry an unsuccessful job
If a destination-specific bulk clone job does not complete successfully, use the Retry action for that job.
Review bulk clone job details
Use the job information action to review the bulk job ID, operation type, destination, overall status, retry count, and field-level outcomes. The details identify the source and cloned rule, object, masking style, masking value, and remarks for each field.

Bulk clone job information

Partially failed job with field-level remarks

Bulk Clone Rules list after job-detail review

Detailed field mappings and masking values

Additional field-level job information
Interpret job results
Result
Recommended review
Successfully cloned
Confirm that the expected cloned rule and masking style are shown for the field.
Partially Failed
Review Remarks to identify failed fields, correct the reported configuration issue, and retry the destination-specific job.
Invalid masking value
Verify that the source masking value is valid for the corresponding destination field. Picklist values must be valid for the destination field configuration.
Key points
Only one source masking rule can be selected for each field type.
A source rule can be applied only to destination fields with the same field type.
Within one destination object, compatible fields of the same type are combined into one cloned rule.
The same cloned rule can therefore mask multiple fields on that destination object.
The total rule count is calculated across the field-type groups of all selected destination objects.
Each destination object is tracked through its own bulk clone job, allowing object-specific monitoring and retry.
Last updated
Was this helpful?


















