Approaches to Performance Analytics with domain separation
Summarize
Summary of Approaches to Performance Analytics with Domain Separation
This guide outlines methods for implementing Performance Analytics with domain separation, allowing for the collection of domain-specific scores while leveraging global or domain-specific records. It is essential for organizations using ServiceNow to manage performance metrics effectively across multiple domains.
Show less
Key Features
- Global Approach: All Performance Analytics records can be stored in the Global domain, with domain separation achieved via specific data collection jobs. The "Run as user" setting determines the domain context for data collection.
- Domain-Specific Approach: Domain users can create and manage their Performance Analytics records. Users in child domains can view but not modify records in parent domains, requiring a domain-specific copy for local use.
- Hybrid Approach: This advanced method allows foundational records to reside in the Global domain while domain-specific records are created in child domains. Successful implementation of global or domain-specific approaches is necessary before applying a hybrid model.
- Record Copying: The PADomainUtils API enables administrators to move or copy Performance Analytics records across domains, enhancing reuse and consistency.
Key Outcomes
By understanding and applying these approaches, ServiceNow customers can customize their Performance Analytics setup to fit their organizational structure, ensuring that relevant metrics are accessible and manageable within the appropriate domains. This leads to improved data visibility and operational efficiency across various roles within the organization.
When using Performance Analytics with domain separation, you can collect domain-specific scores. You can use global or domain-specific Performance Analytics table records or even a combination of both.
Global approach and collecting domain-specific scores
You can keep all Performance Analytics records, such as indicators, breakdowns, and widgets, in the Global domain. In this case, you apply domain separation through domain-specific data collection jobs.
To configure a data collection job to be domain-specific, add a Run as user to the job. The Run as user determines the domain context of where the data collection job runs. For more information, see Create or schedule a data collection job.
You can also specify a domain configuration. Domain configurations are part of the Performance Analytics plugin for domain support, intended to help with complex domain management. For more information, see Associate a domain configuration with a data collection job.
The data collection job collects scores against facts table records in the Global domain. The job also collects scores against records in the domains of the Run as user. The job stores the scores in the domain it collected them from. In data visualizations, a user sees only scores from domains they have visibility into.
If you specify only a Run as user, scores from all child domains are rolled up to the parent. If you also specify a domain configuration, more options are available. For more information about options for collecting and rolling up child domain scores, see Grouping domains in Performance Analytics domain configurations.
Only users with the pa_admin role who are members of one of the domains that the job collects scores for can modify domain-separated data collection jobs. Global users with pa_admin can modify any job.
By default, Platform Analytics Solutions use the global approach.
Domain-specific approach
By using domain-specific Performance Analytics records, you can grant the pa_admin role to domain users to create their own domain-specific components. Users, including administrators, can create and edit Performance Analytics records only within their domain. Users in child domains can read but not edit Performance Analytics records in a parent domain.
You must create a domain-specific copy of a Performance Analytics record to use it in that domain. For example, to add a domain-specific condition to an indicator source, you must create a copy of the indicator and indicator source in that domain.
You can quickly copy an indicator or breakdown and related data from a different domain. Use the Insert and Stay with Relations UI action on the Indicator or Breakdown forms. 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.
com.snc.pa. Only users with the admin or pa_admin roles in the global
domain can see or set these properties.Hybrid approach
A hybrid approach keeps reusable, foundational Performance Analytics records such as indicator sources within the global domain or a parent domain. At the same time, administrators in other domains create domain-specific higher-level Performance Analytics records such as indicators and widgets.
- Bucket groups
- Buckets
- Scripts
- Breakdown sources
- Indicator sources
- Filters
- Breakdowns
- Managed sources
- Manual breakdowns
- Breakdown mappings
- Breakdown relations
Copying Performance Analytics records between domains
You can reuse Performance Analytics records in multiple domains. The PADomainUtils API provides functionality that enables administrators to move or copy Performance Analytics records between domains.