Skip to content

v3.0.0: intel anatomy maps the org's integrations

Latest

Choose a tag to compare

@cclabsnz cclabsnz released this 11 Oct 20:21
· 1 commit to main since this release

intel anatomy now maps an org's integrations. On a real Health Cloud sandbox,
anatomy-fragment.json carried 4 of 59 integration edges; it now carries 32, with the external
systems they reach as nodes. View A also stops drawing a refused read as a measured zero for a
user who cannot see setup.

This is a major because anatomy-fragment.json changes shape (docs/RELEASE.md): a new
integration node kind, integration edges from apexClass.* and org.root as well as products,
and no more anatomy.edges.remoteProxy coverage entry. It requires @cclabsnz/sf-core 0.9.0 or
later on whichever side merges the fragments, since the integration kind changed owner there.

Changed

  • anatomy-fragment.json carries most of the org's integrations, not 4 of 59. An integration
    edge used to need both a product and a Named Credential hop, so on a real Health Cloud sandbox 55
    of 59 were dropped. What changed:

    • The source is now the product the call was traced to; otherwise the Apex class making it
      (apexClass.*, the node intel map emits); otherwise, for a destination configured but never
      found being called, org.root.
    • The destination is a Named Credential (ncred.*) or a Remote Site Setting, emitted as a
      new integration.<SiteName> node. sf-core 0.9.0 gives sf-orgintel that kind.
    • Destinations are keyed by metadata names, never endpoint strings, so no external hostname
      enters the graph.

    On the sandbox: 32 integration links instead of 4, and 20 integration nodes. What's still left
    out is counted precisely.

    This changes anatomy-fragment.json's shape: new node kind, new edge sources, and the
    anatomy.edges.remoteProxy coverage entry is gone. It also requires @cclabsnz/sf-core
    0.9.0.

Fixed

  • A refusal no longer reads as a measured zero for a user who cannot see setup. Such a user
    cannot read Organization. For them:

    • "sObject type 'X' is not supported" is a failed read, not an absent feature;
    • a zero setup count is marked not read, while a non-zero count stands as a lower bound;
    • an empty platform-event list is marked not read.

    View A now draws those tiles hatched "not read" instead of a confident 0. Measured as a
    restricted user: the eight capability tiles and three ops tiles. Users who can see setup are
    unaffected.

  • 90-day record counts are taken for business objects only. Counting a custom metadata type by
    CreatedDate always fails, so every run that touched configuration reported false
    map.recordCounts failures (20 on a real sandbox). Configuration, events and setup objects are
    no longer counted.