Release notes 2026 05 30
Summary
Section titled “Summary”This initial BoomiSight release helps Confluence teams bring Boomi runtime, deployment, execution, API, connector, and release context into space dashboards and runbook macros. Space admins can configure Boomi access once, verify which feature areas are available, and let authors add focused Boomi evidence to Confluence pages.
What Changed
Section titled “What Changed”- Space-scoped Boomi configuration with account ID, username normalization, secret token storage, refresh interval, and dataset flags.
- Verify Connection & Access diagnostics that report basic connectivity, runtime/deployment access, deployment history, execution monitoring, and API governance enrichment separately.
- BoomiSight global landing page with configured spaces and documentation, support, and demo links.
- BoomiSight space dashboard with Environment Comparison, Execution Dashboard, API Governance, Diagnostics, and Connector Inventory tabs.
- Environment comparison metrics, severity-aware drift rows, environment filters, drift-only filtering, refresh, CSV export, and HTML export.
- Execution dashboard with time window, status filter, environment filter, run counts, error rate, top failing processes, top failing runtimes, top error signatures, and recent execution rows.
- API Governance view for API counts, drifted APIs, undocumented APIs, APIM plan coverage, and partial APIM information when that endpoint is unavailable.
- Diagnostics view for module health, source errors, partial coverage, and informational source messages.
- Connector Inventory view for connector types, process counts, connector actions, and sample processes.
- Detailed and compact macros for process snapshots, atom health, environment summaries, and API snapshots.
- Process-focused macros for deployment history, executions, blast radius, business health badge, release notes, and integration landscape summary.
- Scheduled sync that refreshes cached Boomi data according to the per-space refresh interval.
- Marketplace licensing checks around paid app surfaces and Boomi data access.
Improved
Section titled “Improved”- Boomi token username handling accepts raw usernames or Boomi token-auth usernames and stores a normalized username.
- Connection verification distinguishes valid-but-limited Boomi identities from complete failures.
- Optional APIM access is treated as enrichment rather than a hard blocker for core runtime and deployment views.
- Macro configuration uses searchable Boomi resources when cached data is available, with manual ID and URL fallback fields for controlled authoring.
Admin Action Required
Section titled “Admin Action Required”For a new installation, install BoomiSight from Atlassian Marketplace, open BoomiSight Configuration in each target Confluence space, enter the Boomi account ID, username, and API token, choose dataset flags, save, then run Verify Connection & Access.
For existing evaluation installations, review each configured space after upgrading, verify the stored token state, and run a dashboard refresh so macros and dashboards use current cached data.
Compatibility and Upgrade Notes
Section titled “Compatibility and Upgrade Notes”- BoomiSight is built for Confluence Cloud and Boomi Platform API access.
- The app stores configuration and cached data per Confluence space in Atlassian Forge storage.
- The Boomi API token is stored as a Forge secret and is not returned to the configuration UI after save.
- External API calls are limited to the Boomi API host used by the app.
- Paid Marketplace licensing is enabled for production installations. Unlicensed or expired installations may see paid app surfaces blocked until licensing is valid.
- APIM metadata is optional. If APIM endpoint data is unavailable, API Governance can still show Platform API-derived rows and mark enrichment as partial.
Known Limitations
Section titled “Known Limitations”- Execution dashboards and execution-backed macros show empty states when the selected Boomi account has no recent executions in the chosen time window.
- API Governance may show partial enrichment when APIM endpoints are not available for the tenant or identity.
- Macro auto-conversion depends on Confluence editor behavior. If a pasted Boomi URL does not convert, insert the matching BoomiSight macro manually and configure it with the same resource details.
- Compact macro layouts can be affected by narrow Confluence columns.
Validation
Section titled “Validation”- Verified configuration, access diagnostics, global landing page, all dashboard tabs, and a rendered Integration Landscape Summary macro in a live Confluence tenant.
- Verified the docs pack includes screenshots, focused crops, videos, a macro reference, tutorials, installation/configuration/uninstallation guidance, support guidance, release notes, and an evidence matrix.
- Verified source coverage against BoomiSight manifest modules, resolver actions, dashboard source, settings source, and macro configuration source.