Create an Anonymization Template and Execute an Anonymize Job

Create and configure an Anonymization template for Salesforce by specifying objects and sensitive fields with replacement values. Use the Anonymization template to mask sandbox data in a standalone anonymize job, or reference the Anonymization template in a seeding template to anonymize the source data prior to it being seeded.

1. Start the process by signing in to your Backup & Recover Platform.
2. In the menu bar along the top of the UI, click Anonymize and then, in the Templates tab, click the + New Template… button.
3. In the article Work with Anonymization Templates for Salesforce, follow the procedure provided in the topic Create an Anonymization Template for Salesforce.
   

   Tip In the Description field of the New Anonymization Template dialog, we recommend listing those objects whose fields you want to mask. Focus on adding objects that contain PII/sensitive/classified information, for example, Contact.
4. With your newly created anonymization template displayed in the UI, configure it to address your organization’s specific data masking needs. Continuing in Work with Anonymization Templates for Salesforce, follow the procedure provided in the topic Configure an Anonymization Template for Salesforce.
   1. While building your template, remember to periodically click Save so that recently applied updates are saved.
   2. The Configure an Anonymization Template topic provides a bunch of anonymize features to learn about:
      • Fill if Empty: Option Details
      • Picklist Fields in an Anonymization Template
      • Dependent Picklists
      • Defining Object Record Filters in Anonymization Templates
      • Viewing Object Record Filters
5. Now, execute your first anonymize job. You’re going to be executing a standalone anonymize job using your newly created anonymization template. Follow the procedure and explanations provided in Define and Execute Anonymize Jobs.
   

   Important Standalone anonymize jobs are typically used when either data seeding to a sandbox is not needed or has already been executed to that sandbox. So go ahead and mask PII/sensitive/classified data that already exists in a destination sandbox of your choosing.

   When considering disabling Salesforce automations in the Automations section of the <template name> window, take note of the following:

   • If you select to disable all automations, then all Validation Rules, Workflows, Triggers and Processes, with the exception of Triggers and Processes that are part of managed packages, are automatically disabled for the destination sandbox environment during anonymization processing and automatically re-enabled upon processing completion.
   • The anonymization job may take several more minutes to disable all Validation Rules, Workflows, Triggers and Processes.

   

   Warning If you abort an anonymize job before it has completed, anonymize processing cannot re-enable the selected automations that it previously disabled.
6. After clicking the Anonymize button, the UI displays the Activities tab. This tab contains an entry for your anonymize job that reports a bunch of details about the job. Read about the tab’s reported information in the topic Define and Execute Anonymize Jobs that is provided in the article. Also, read about Anonymize Job Reporting.