Identify which Salesforce production orgs or sandboxes to use as data sources or destinations for seeding jobs. Determine the most suitable seeding templates, whether pre-defined templates (starter, CPQ, FSL, nCino) or custom Levels or Nodes templates. And determine which sandboxes need anonymization along with the object field types to be anonymized. Seed relevant data from production orgs or sandboxes into Developer, Developer Pro, Partial, and Full sandboxes, and even into production orgs.
- Plan for Success: It’s important to consider and identify what data needs to be seeded and what data needs to be anonymized. Reuse seeding and anonymize templates, update existing templates, as needed, to suit current product development needs, anonymize sensitive data, continuously update data, and manage seeding job size.
- Define Seeding Needs: Identify the types of objects and their records that are needed for sandbox development. Determine how often and at what scale these objects/records will be used for testing. Check if the objects contain fields that hold sensitive/PII data, for example, credit card numbers, phone numbers, or email addresses. Make note of these object fields to later create and configure an anonymization template to apply on that data and ensure it is protected.
- Common Use Cases: Identify a comprehensive set of use cases for the data, both typical,
custom and special cases.
- Seeding Attachment, Document, and ContentDocument Objects: Replace original files with dummy files of the same type during seeding, safeguarding PII by preventing access to actual data. For ContentDocument objects, you have the option to seed original files.
- Seed using pre-defined Nodes templates - starter templates for common objects, or templates that specifically seed either CPQ objects, FSL objects, or nCino objects.
- Seed data to Full Copy sandboxes, on a recurring basis, for the most live and up to date production data by scheduling daily and/or weekly seeding jobs.
- Seed the most relevant production data to developer environments for your team to test specific use cases with precision and efficiency.
- Anonymize email addresses to avoid accidental emails being sent to contacts while testing using sandbox data.
- Perform either standalone anonymization jobs or anonymize as part of a seeding job.