Space Configuration and Access Diagnostics

Use the configuration page when a space needs to connect to Boomi, rotate a token, change dataset coverage, or prove which BoomiSight features the current Boomi identity can support.

Outcome

A space admin can save Boomi credentials, keep the token secret, select dataset flags, and run diagnostics that distinguish core access from optional enrichment.

Where To Open

Open the Confluence space, then go to Space settings, Apps, BoomiSight Configuration.

Guided Flow

1. Enter the Boomi account ID, Boomi username, API token, refresh interval, and dataset flags.

2. Save the configuration. BoomiSight stores the API token as a secret and later shows only that a stored token exists.

3. Run Verify Connection & Access.

4. Read the feature readiness lines before enabling teams to rely on dashboards or macros.

Diagnostic Areas

• Basic API authentication confirms the token can authenticate.
• Core runtime and deployment dashboards support environment comparison, atom health, environment summaries, and picker-first macro configuration.
• Deployment history and release notes support deployment timelines and release-window macros.
• Execution monitoring supports execution dashboards, process executions, and business health badges.
• API governance enrichment adds APIM details when the Boomi tenant and identity support those endpoints.

Success Checklist

• The API token is not visible after save.
• The refresh interval matches the desired cache cadence.
• Runtime, API, execution, and connector dataset flags reflect the team’s intended coverage.
• Verify Connection & Access returns clear feature-area statuses.
• Any limited or partial area is either expected or assigned to an admin for Boomi permission review.