Skip to main content

Preflight checks for Workday Prism Analytics

TL;DR

Before running the Workday Prism Analytics crawler, Atlan checks that it can reach your tenant, that Prism Analytics is licensed, and that the configured account has permission to read tables and Data Change Tasks.

Connect

Before running the Workday Prism Analytics crawler, you can run preflight checks to perform the necessary technical validations. The following preflight checks are completed, in this order:

Reachability

Atlan requests an access token from your Workday tenant's OAuth 2.0 token endpoint, using the Client ID, Client Secret, Refresh Token, and Base URL you provided.

Check successful if Atlan obtains an access token.

Check failed if the token endpoint can't be reached, or the credentials are rejected. Since this same token request also gates the Tenant version check, a failure here fails that check too.

Tenant version

Confirms that the token response resolves to a valid Workday tenant.

Check successful if the access token request in the Reachability check succeeds.

Check failed if Atlan can't obtain an access token—see Reachability earlier on this page.

Prism licensed

Atlan calls GET /tables?limit=1 against your tenant.

Check successful if the call returns HTTP 200.

Check failed for HTTP <code> if the call fails—most commonly because Prism Analytics isn't licensed for this tenant, or because your API client's scope doesn't include Prism Analytics.

Permission tables

Uses the result of the same GET /tables?limit=1 call as Prism licensed: a 200 response confirms both that Prism is licensed and that the Integration System User has Get access to the Domain Security Policies gating Prism tables.

Check successful if the call returns HTTP 200.

Check failed for HTTP <code> if the call fails—most commonly a missing grant on the Prism Access Security Group.

Permission data changes

Atlan calls GET /dataChanges?limit=1 against your tenant.

Check successful if the call returns HTTP 200.

Check failed for HTTP <code> if the call fails—most commonly a missing grant on the Integration System Security Group for Data Change Task-related Domain Security Policies.