Skip to main content

Global Analysis

Object pages document the org one component at a time. Global analysis steps back and describes the org as a whole: what it is for, who uses it, and where its complexity concentrates.

The result is the Org Functional Overview, found in the Org synthesis domain of the documentation in the portal. It is produced automatically with every scan, on every plan; there is nothing to turn on.

What the overview contains​

Functional picture​

Written by an AI model from the documentation of the whole org:

  • Functional Domains -- the main business areas the org supports.
  • Key Capabilities -- what the org lets its users do.
  • Actors -- the people and roles involved.
  • Main User Journeys -- the typical paths through the org, with their actors and outcome.

An actor that cannot be matched to a profile, permission set or permission set group of your org is marked (inferred), so you can tell a documented role from an educated guess.

Org snapshot​

Key figures for the org: business objects, business rules, functional processes, external integrations, Experience portal sites, API classes, and batch or scheduled jobs, with a link to the process catalog.

Signals computed from the metadata​

These sections are computed deterministically, without AI:

  • Functional duplication risks -- pairs of objects with very similar names and a large share of common fields, which may cover the same business domain twice. The page suggests deciding which one is the source of truth.
  • Execution complexity hotspots -- the entry points that can reach the largest part of the org (depth, reachable components, writes to other objects, platform events published). This measures where complexity concentrates, not where time is spent at runtime.
  • Non-idempotent batches -- batch, scheduled and queued jobs whose re-run on the same input could create duplicates, increment counters or republish events. This is a prediction from the code, not a runtime observation.
  • Consolidated actors and roles -- profiles, permission sets and permission set groups with active users, cross-referenced with the journeys, with their number of active users and objects reached. Purely technical grants are listed separately.

Perimeter​

To analyze the whole org at once, aprity uses a model with a very large context window. On very large orgs, some elements may still not fit; they are listed under Global analysis perimeter on the Coverage and fidelity page. Their own pages are unaffected -- only the org-wide narrative did not see them.

When to use it​

  • Getting a first understanding of an org you do not know.
  • Preparing an architecture review or a migration scoping.
  • Finding duplicated business areas or batch jobs that are risky to re-run.
  • Explaining the org to non-technical stakeholders.

Related: Functional Processes, Org Metrics.