Org Metrics (Overview)
Org metrics is the first entry of the portal rail. Where Documentation opens the content, this page answers three questions about the org itself for the selected version: what it holds, how much of it is custom, and how far it sits from the platform standard.
Volumes
Four headline figures, measured on the selected version:
- Documented objects
- Business rules
- Processes -- the functional processes identified in the org.
- External systems -- the systems your org calls or is called by (see Integration Map).
Specific KPI
A card summarizes the org's custom footprint: how many components your teams built on top of the standard platform. Managed packages are excluded. Open it (See the detail) for the full view:
- Counters by category -- specific (org-authored) versus managed components, per metadata type, with a % specific ratio where the full population can be measured reliably (fields and objects).
- Drift since previous scan -- components added, removed and modified since the previous scan.
- Specific-footprint trend -- how the footprint evolves scan after scan.
- Where the custom footprint piles up -- how custom fields are concentrated across objects, with the most loaded objects.
- Concurrent mechanisms on save -- objects on which several automation technologies run when a record is saved.
These counters are deterministic: they are computed from the scan, against a counting catalog that is identical for every customer. When the comparison between two scans is not meaningful (first scan, different scan scope, incomplete retrieval, catalog change), the page says so instead of showing a misleading difference. On the Intelligence plan, a short written reading of the trend is added.
The Specific KPI is included on every plan.
Good to know
- Figures always refer to the version selected in the portal. Switch versions to compare.
- If a figure could not be measured for a version, the page says so rather than showing zero.
- For what the scan covered and skipped, see Coverage and fidelity.