Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Performance analytics with domain separation

Log in to subscribe to topics and get notified when content changes.

Performance analytics with domain separation

When using Performance Analytics with domain separation you can collect domain-specific scores, and use global or domain-specific configuration records such as indicators, breakdowns, and dashboards.

Note: You must have the premium version of Performance Analytics to use Performance Analytics in any domain other than global.

Collecting domain-specific scores

Data collector jobs can access records based on the roles, entitlements, and domain of the user selected in the job Run as field. To collect scores from a particular domain, ensure the Run as user is a member of that domain.

The domain of each data collector job determines the domain of scores generated by that data collector. The domain of the source records do not affect the domain of the scores.

Global configuration

By using configuration records in the global domain, you can present domain-appropriate data automatically.

To populate the data, create a separate data collector job for each domain. Ensure each user selected in the Run as field is a member of the correct domain. The collected score is recorded under the domain of the Run as user. When a user in a domain views a widget or scorecard, only scores from that user’s domain appear.

By default, configuration records from Performance Analytics content packs use the global domain.

Domain-specific configuration

By using domain-specific configuration records, you can grant the pa_admin role to domain users to create their own domain-specific components. Users, including system administrators, can create and edit configuration records only within their domain. Users in child domains can read but not edit configuration records in a parent domain.

You must create a domain-specific copy of a configuration record to use it in that domain. For example, to add a domain-specific condition to a indicator source, you must create a copy of the indicator and indicator source in that domain.

You can quickly copy indicator and related data from an indicator in a different domain using the Insert and Stay with Relations UI action on the Indicator form. Any breakdowns, breakdown exclusions, or time series exclusion relationships are also copied. Any associated scheduled jobs are copied only if the Run as user for that job is the current user.

To collect scores, create a new data collector job associated with the domain-specific indicators.

Hybrid configuration

By using a hybrid configuration you can maintain reusable foundation configuration records such as indicator sources within the global domain or a parent domain while allowing administrators in other domains to create domain-specific configuration records such as indicators and widgets.
Note: The hybrid configuration is an advanced option. Implement either the global or domain-specific configurations successfully before attempting to use a hybrid configuration.
When using a hybrid configuration, foundation records should be managed only within the global domain or a parent domain. All other configuration records, such as widgets and indicators should be managed separately within each child domain. The following record types are considered foundation records.
  • Bucket groups
  • Buckets
  • Scripts
  • Breakdown sources
  • Indicator sources
  • Filters
  • Breakdowns
  • Managed sources
  • Manual breakdowns
  • Breakdown mappings
  • Breakdown relations

Copying configuration data

You can reuse Performance Analytics configurations in multiple domains. The PADomainUtils API provides functionality that allows system administrators to move or copy Performance Analytics configuration records between domains.