Documentation Health and Page Context
BoomiSight separates quick page-local context from an admin-initiated space scan. The Boomi Architecture and Boomi APIs bylines describe the current page; Documentation Health summarizes cached findings from the last completed scan of the configured space.
Page-Local Bylines
Section titled “Page-Local Bylines”Open the Boomi Architecture or Boomi APIs byline below a Confluence page title to review the Boomi context genuinely associated with that page.

The bylines can show:
- BoomiSight macros and visible Boomi links found on the current page.
- Missing macro configuration or links that need review.
- Page-local API context and cached API posture when API evidence exists on the page.
- Documentation Health and freshness signals for the page.

Choose Refresh page context when the page has changed and the popup needs to reread it. This action reads the current Confluence page only. It does not scan the space, edit the page, or contact Boomi.
If BoomiSight cannot associate cached context with the current page, it reports the state as unknown or not cached. It does not substitute unrelated space-wide counts or treat missing evidence as zero.
Documentation Health
Section titled “Documentation Health”Open BoomiSight Dashboard, then Documentation Health.

Use the two actions for different jobs:
- Scan Space Pages starts a bounded, space-admin scan of current Confluence pages. It looks for BoomiSight macros, visible Boomi links, source references, API/APIM links, configuration gaps, and review signals.
- Refresh Cached Snapshot reloads the most recent stored scan result. It does not reread page bodies or claim that a new scan occurred.
The summary can highlight pages needing attention, stale page context, missing macro configuration, raw links without a governed macro, partial API posture, and pages with no Boomi context. Open a finding through its Confluence page link to review the actual page.
Permission And Data Boundary
Section titled “Permission And Data Boundary”- Page reads use the current user’s trusted Confluence context and existing Confluence access controls.
- Only a space admin can start the bounded space scan.
- The scan defaults to at most 200 pages and never exceeds 250 pages in one run.
- BoomiSight stores compact page metadata, counts, freshness, and findings. It does not store full Confluence page bodies as Documentation Health results.
- Neither page-context refresh nor Documentation Health edits Confluence pages or calls Boomi.
Interpretation Tips
Section titled “Interpretation Tips”- A healthy page-level result means the cached page facts support that result; it is not a guarantee that the wider space or Boomi tenant is healthy.
- A stale scan may still be useful for triage, but run Scan Space Pages before relying on it for a current review.
- No Boomi context is not automatically a defect. Many ordinary Confluence pages are not intended to document Boomi.
- Use page bylines for the current page and Documentation Health for the scanned space. Do not compare their counts as if they were the same scope.