Scan Strategy: What to Document First
A well-planned scan strategy ensures you get the most value from aprity. This guide helps you prioritize what to document first and how to build a sustainable documentation practice.
Start with Your Core Objects
A paid-plan scan documents the whole org at once, so you do not select objects per scan -- instead, focus your review on the Salesforce objects that drive your business:
- Revenue-critical objects — Account, Opportunity, Quote, Order
- Customer-facing objects — Case, Contact, Lead
- Custom objects with complex automation — Objects with multiple triggers, flows, and validation rules
On a Trial, where you can document only 3 objects in total across the whole trial, this priority list is also your object-selection guide.
Objects with the most automation (triggers, flows, validation rules) benefit the most from aprity documentation because they are the hardest to understand manually.
Recommended Scan Progression
Each scan already documents the whole org, so this progression is about where you focus your review week over week.
Week 1: Core CRM
After your first whole-org scan, review the primary CRM objects to familiarize yourself with aprity's output quality.
Week 2: Custom Business Logic
Review your custom objects and any objects with complex automation chains. Use the Execution Graph to understand trigger execution order.
Week 3: Integration Points
Review objects involved in external integrations — API endpoints, external services, and cross-system data flows. The Integration Inventory mini-sites surface these.
Week 4: Security and Compliance
Review the permission sets, profiles, and sharing rules captured by the Security Baseline. Use the output for compliance documentation.
Scan Frequency Recommendations
| Org Change Frequency | Recommended Interval |
|---|---|
| Daily deployments | Weekly scans |
| Bi-weekly releases | Every 2 weeks |
| Monthly releases | Monthly scans |
| Stable/mature org | Monthly scans |
Multi-Org Strategy
For organizations with multiple Salesforce orgs (all plans support one org per tenant):
- Production first — Always document your production org as the source of truth
- Sandbox for validation — Run a scan on your sandbox after major deployments to preview changes
- Separate docs per org — Each org gets its own documentation set
Using Business Rule Evolution
Every plan includes Business Rule Changelog, which tracks how your business rules change between scans. Enable this feature in the Analysis Configuration to:
- Detect rule additions and deletions between scans
- Track changes in validation logic over time
- Build an audit trail for compliance
Common Mistakes to Avoid
- Scanning everything at once on a Trial plan (you only have 4 scans total)
- Ignoring the Feedback feature — Use it to improve documentation quality over time
- Not scheduling recurring scans — Documentation becomes stale without regular updates