What is an easy way for a responsible user to get real-time updates on the signals for a particular KPI?
As a responsible user, you can receive email notifications about new or unresolved signals, anti-signals, or any actions taken on signals.
You can configure how frequently you get these reminders and the maximum number of reminders to get for a signal.
You no longer have to open KPI Signals and manually check each KPI for signals.
Scheduling a report for the signal data does not provide real-time updates.
Manually check the KPI for signals and monitoring the signal score on a dashboard requires the user to constantly check for the updates without a pause, which is not easy.
How does KPI Signals support notifications?
To support notifications, the KPI Signals application provides automated signal detection jobs. For formula indicators, you can modify the jobs to line up with the data collection jobs for the contributing indicators.
The KPI Signals application includes jobs that detect signals automatically. These jobs run so responsible users can be notified of new signals without opening the application. The job for signals on formula indicators requires scheduling.
When you view an indicator in KPI Details and open the KPI Signals panel, that indicator is checked for signals. You, therefore, always have the most up-to-date signals. However, the KPI Signals application also has automated signal detection jobs. These jobs send notifications about signals to subscribed users without them having the application open.
Which of the following are true statements about configuring pie, donut, and single score visualisations in workspaces?
A pie visualisation shows how individual pieces of data relate to the whole using a circle to represent the whole.
A Donut visualization shows how individual pieces of data relate to the whole using a donut shape to represent the whole.
Single score visualisations display a single, key business value or current aggregate indicator score. You can set a score to update in real-time.
The following enhancements are made to pie, donut, and single score visualisations in the Quebec release:
* The metric label name is displayed near the metric value.
* Legend percentages are shown along with values.
* Data labels are shown as only percentages, as values, or as both.
Gradient, texture, or no colour are not valid colour options for data display.
You can set 'default', 'colour palette' and 'fixed element colour' for pie and donut visualisations, and 'default' and 'single colour' for single score visualisations.
Which of the following items can you view without the pa_viewer role if the indicator and breakdown ACLs are respected? (Choose two.)
You can rely less on roles and more on access control lists (ACLs) to secure Performance Analytics.
On new instances, you no longer need the pa_viewer role to view the following items. Instead, indicator and breakdown ACLs are respected:
* Analytics Hub
* Text Analytics widgets
* KPI Details
* Breakdowns on workbench widgets
Performance Analytics widgets: In general, Performance Analytics widgets follow indicator and breakdown ACLs.
Targets and Thresholds: On the Analytics Hub, no roles are required to create personal targets and thresholds.
What condition do you use on the Elements Filter record for the 'Groups' Breakdown Source to get only groups that had an incident assigned to them?
When you create an element filter, you can include conditions on a related field in a different table than the breakdown source table.
Element filters enable you to limit the displayed breakdown elements on an Analytics Hub or widget using filter conditions, including personalised visuals.
You can select an element filter when viewing breakdowns on an Analytics Hub or configuring a breakdown widget.
For example, you could create an element filter on the Groups breakdown source, which uses the Group [sys_user_group] table. If you added a related list condition on Incident [incident]->Assignment group, you would get only groups that had an incident assigned to them. If this condition included [[Created][on][Last 6 Months]], you would get groups that were assigned an incident that was created within the last six months.
