Repository navigation
v2.0.0: intel map describes the business model, not its plumbing
intel map now describes the org a Salesforce architect would recognise. It used to count every
pair of objects any Apex class or flow touched, test classes included, and to treat User,
RecordType and Share objects as peers of the business model. On a real Health Cloud sandbox it
reported 212 objects and 2,171 coupled pairs in 57 domains. This release reports 95 business
objects and 620 couplings in 17 domains, and states the rest as what those objects depend on.
This is a major because graph-fragment.json changes shape and meaning (docs/RELEASE.md).
If you read it:
couplesedges join business objects only. For an unchanged org, expect fewer pairs and
different endpoints.- Pairs with an actor, record type, setup object, configuration, event or reference data are
newusesedges, each carryingattrs.roles. - Each touched object's role and its evidence arrive as
attrs.orgintel.objectRoleonce
merged, together with newmap.objectRoles.*andmap.apexClasses.testscoverage entries.
If you import the package, IntelContext.orgInfo is now OrgInfo | null. The HTML report of a
run with no roles decided is unchanged, byte for byte.
Changed
-
intel mapclassifies objects from platform evidence, and only business pairs are
couplings. Each object this run touches gets a role from sf-core'sclassifyObject, decided
from what the platform reports, never from its name:describeGlobal's parent entity, plus layout and trigger capability;- the
EntityDefinitionsharing model; - what the
OwnerId,CreatedByIdandRecordTypeIdfields point at; - whether production automation only reads the object.
What that changes:
- Companions fold into their parent.
AccountSharecounts asAccount. - Pairs with an actor, a record type, setup, configuration, an event or reference data are
written asusesedges instead ofcouples, and the report states them in a new "What the
business objects depend on" section. - Each object's role and its evidence are contributed as
attrs.orgintel.objectRole. - A refused fact read degrades to
unclassified, recorded undermap.objectRoles.*. An
unclassified object stays among the couplings.
On a real Health Cloud sandbox, together with the test-class fix below, the map went from 212
objects and 2,171 coupled pairs in 57 domains to 95 objects and 620 pairs in 17 domains, with
UserandRecordTypeout of the backbones. Expectcouplescounts, domains and backbones to
change for an unchanged org. Specified indocs/OBJECT_ROLES_SPEC.md.
Fixed
-
Apex test classes are no longer analysed as production automation. A test class inserts
fixture data for many objects at once, so its object references are not couplings in the running
org. On a real Health Cloud sandbox 445 classes were tests, and excluding them took the map from
2,171 coupled pairs to 1,231. A class is a test when the platform marks it so (the SymbolTable's
IsTestannotation ortestMethodmodifier, or an@isTestclass declaration in the body),
never by name. Test classes are listed but not analysed, and reported once in the notes and as a
map.apexClasses.testscoverage entry. ExpectapexClassesAnalyzedand every coupling count
to drop for an unchanged org. -
"Top process backbones" in the terminal summary lists the heaviest couplings. It printed the
first eight edges in id order, which on a real org meant weight-1 pairs whose names sorted first. -
intel mapandintel anatomyrun for a user without View Setup and Configuration. Every
command readOrganizationfirst, and the platform refuses that object to such a user, so the
tool stopped before reading anything. That ruled out running it as the restricted users whose
view of an org it exists to describe. Both commands now take the org id from the connection's
auth info, name the org by its id, and say why in the run's notes.intel probeand
intel discoverreport edition and sandbox status, which cannot be guessed, so they still
stop, now naming the missing permission instead of printing the platform's bare
sObject type 'Organization' is not supported.IntelContext.orgInfois nowOrgInfo | null. -
intel anatomyreads Sites again. From0.3.0the channels collector queried
SELECT Name, SiteName, Status FROM Site.Sitehas noSiteNamecolumn (the field belongs to
RemoteProxy), so the read was refused withINVALID_FIELDon every org, and the channels band
reported a failed read even where the org had sites. It now readsName,MasterLabeland
Status:MasterLabelis the label shown as the channel name, andName, the site's unique
technical name, keys thesite.*node. The unit fixture had invented the missing column, which
is how this shipped green; the new test's mock refuses any columnSitedoes not have, as the
org does. Found by running View A against a live org. -
graph-fragment.jsonnow marks whatintel mapdropped. The fragment hardcoded an empty
coverage, so every drop the run detected reached the terminal and the HTML report and stopped
there. Merged withintel anatomy's census, a refusedFlowDefinitionViewread looked the same
as an org with no active flows:analysed.flows: 0and nothing to explain it. Each drop is now
also acoverage.unavailableentry, the same wiringanatomy-fragment.jsonalready had.
failedmeans the read was tried and refused.deferredmeans it was never tried.Scope Reason When map.flowsfailed the flow listing was refused map.flows.manageddeferred managed-package flows, whose metadata is never requested map.flows.metadatafailed one entry per flow whose metadata was refused, empty or unparseable map.flows.subflowsdeferred referenced subflows that were never retrieved, so their touches are not inherited map.apexClassesfailed the class listing was refused map.apexClasses.unreadablefailed classes with neither a readable body nor a SymbolTablemap.apexTriggersfailed the trigger listing was refused map.apexTriggers.unresolvedObjectfailed one entry per trigger whose object could not be resolved map.automationCounts.<field>failed a refused automation query, so that count is an unmeasured 0on every objectmap.recordCountsdeferred the sweep was capped by --max-node-countsmap.recordCountsfailed 90-day counts that were refused and fell back to 0map.objectsfailed the sObject catalog was refused Entries are sorted by scope, then reason, then detail, so the bytes stay stable across runs
even though flow metadata is fetched concurrently. A run that drops nothing still writes an
emptycoverage. -
Two silent fallbacks in
intel mapare now reported. A refused 90-day record count was
stored as0with no note anywhere. A refused sObject catalog read meant running with no
known-object set, which pushes every Apex class onto the regex fallback, also without a note.
Both now appear in the run's notes and in the fragment's coverage.