How to Select Metadata Types for a Scan
When launching a scan, aprity automatically detects and extracts the most relevant metadata types from your Salesforce org. This guide explains how metadata selection works and how to optimize your scan scope.
Default Behavior
By default, aprity scans all supported metadata types in your org:
- Apex Classes — Business logic and controllers
- Apex Triggers — DML event handlers
- Validation Rules — Field-level data validation
- Flows — Record-triggered and screen flows
- Process Builders — Legacy automation (deprecated by Salesforce)
- Custom Objects — Object definitions and field schemas
- Permission Sets — Access control definitions
- Profiles — User permission profiles
Scan Scope
The Documentation and Intelligence plans document the whole org at full depth — there are no metadata item caps per type. The Trial plan applies the same analysis depth but documents only 3 objects total, so prospects can evaluate quality without harvesting the full org for free.
Whole-org coverage at full analysis depth is included on the Documentation and Intelligence plans, with no per-metadata-type item caps. On Trial, documentation is limited to 3 objects.
Optimizing Your Scan
For large orgs, consider these strategies:
- Start with core objects — Focus your review on the objects that drive your business processes (the Functional Processes section is a good entry point).
- Use multiple scans — Run separate scans for different functional areas if you want separate documentation sets.
- Leverage scheduling — Set up recurring scans to keep documentation current (available on Documentation and Intelligence plans).
What Happens During Metadata Extraction
- aprity connects to your org via JWT Bearer authentication
- It queries the Tooling API to discover metadata components
- Dependencies between components are automatically resolved
- A dependency graph is built before AI analysis begins
The entire metadata extraction phase typically takes 1-3 minutes depending on org size.