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 by Plan
The number of metadata items per type is limited by your plan:
| Plan | Max Items per Type |
|---|---|
| Trial | 100 |
| Starter | 100 |
| Professional | 500 |
| Enterprise | Unlimited |
info
If your org has more metadata items than your plan allows, aprity prioritizes the most recently modified items.
Optimizing Your Scan
For large orgs, consider these strategies:
- Start with core objects — Focus on the objects that drive your business processes
- Use multiple scans — Run separate scans for different functional areas
- Leverage scheduling — Set up recurring scans to keep documentation current
tip
If you need to document more than your plan allows, consider upgrading to Professional or Enterprise.
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.