Installation
Install BoomiSight from Atlassian Marketplace. During pre-launch evaluation, Flowdence may install a development or staging Forge environment into an internal Confluence site for validation.
After installation, each Confluence space that uses BoomiSight must be configured from Space settings. The app includes a global landing page, a space dashboard, space-scoped settings, scheduled sync, page bylines, Boomi macros, and BoomiSight Specialist for Rovo-enabled sites.
Prerequisites
Section titled “Prerequisites”- Confluence Cloud with permission to install and configure apps.
- A Boomi API identity with Platform API access.
- A Boomi API token for that identity.
- Space admin permission in each Confluence space that will use BoomiSight.
Boomi permissions can be broad or limited. BoomiSight reports available, limited, unavailable, and unsupported feature areas after configuration instead of treating every optional permission gap as a total failure.
Installed Capabilities
Section titled “Installed Capabilities”BoomiSight adds:
- A global BoomiSight page for configured-space discovery.
- A BoomiSight Dashboard page in each configured Confluence space.
- BoomiSight Configuration in space settings.
- Boomi Architecture and Boomi APIs bylines on pages in configured spaces.
- Documentation Health with an explicit space-admin page scan and cached findings.
- Detailed and compact macros for Boomi processes, runtimes, environments, APIs, deployments, executions, connector blast radius, landscape summary, business health, and release notes.
- A Custom Process Properties and XREF macro that displays safe structural facts while keeping raw values hidden.
- BoomiSight Specialist for cache-first current-page and current-space questions when Rovo is available and enabled for the site.
Marketplace licensing is enforced for paid app surfaces in production.
Atlassian Permission Purposes
Section titled “Atlassian Permission Purposes”Atlassian may ask a site admin to approve these capabilities during installation or a major upgrade:
| Permission | Customer-facing purpose |
|---|---|
| App storage | Store each space’s configuration, protected credential reference, cache, freshness state, and configured-space registry data in Atlassian Forge. |
| Read Confluence spaces | Use trusted current-space context and verify space-admin access for configuration and maintenance actions. |
| Write Confluence spaces | Create or remove one BoomiSight configured-space marker. The marker controls whether configured-space surfaces such as bylines are shown. |
| Read Confluence pages | Read the current page for page-local bylines and confirmed page-context refreshes, and read a bounded set of pages only when a space admin starts a Documentation Health scan. |
BoomiSight 3.0 does not request Confluence page-write access. Page-context refresh and Documentation Health scans do not edit Confluence page content.
Upgrading From An Earlier Version
Section titled “Upgrading From An Earlier Version”- Approve the Marketplace upgrade and the Confluence space-write permission if Atlassian presents an approval screen.
- In each previously configured space, open BoomiSight Configuration and save the existing complete configuration once. This creates the configured-space marker used by the new bylines and configured-space surfaces.
- Run Verify Connection & Access.
- Open Documentation Health and run Scan Space Pages before expecting page findings.
Existing Process Snapshot macros keep their previous presentation. Authors must deliberately enable Include configuration dependencies on a detailed Process Snapshot when they want current-Build Process Property and XREF relationships.