Pass the ServiceNow Certified Application Specialist CAS-PA Questions and answers with ExamsMirror

A breakdown source is defined as a set of records from a table or database view or as a bucket group. Multiple breakdowns can use the same breakdown source.

Breakdown sources specify which unique values, called breakdown elements, a breakdown contains.

Breakdown source records have a related list that lists the breakdowns that are based on that source. You can create a breakdown by selecting the ‘New’ button while in this list. The list works like the Indicators list on indicator source records.

Other options in this question do not exist on the breakdown source form.

After you create breakdowns that use this source, these breakdowns are listed in the Breakdowns tab.

par_vis_config.data_source.can_select_indicator property specifies roles (comma-separated) which can select indicators as data sources from the Data Visualisation configuration panel. If empty, all users can select the indicator sources that they have access to.

Type: string

Default value: empty

Location: System Property [sys_properties] table

com.snc.pa.dc.max_row_count_indicator_source property sets the maximum number of rows allowed to be fetched from an Indicator Source.

glide.source_control.checksum_required property allows you to enable optional checksum validations and sanitisations.

glide.knowman.search.apply_role_based_security property honours read access to knowledge bases or articles specified for roles if set to true. If false, it enables specified user criteria to override read access specified for roles.

You no longer have to activate the KPI Signals (com.snc.pa.kpi_signals) plugin. It is active by default.

If you do not want this feature, request a Now Platform administrator to set the property com.snc.pa.activate_kpi_signals to false. Because this property does not exist by default, the administrator must add it.

If you reactivate KPI Signals, signal detection resumes from the time you originally deactivated the feature, not from the time you reactivated it.

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.

‘Show score update time’ shows the timestamp of when the score was last updated.

‘Follow filters’ set for a workspace page. When enabled, the visualisation displays on a workspace with the filters set by the page. Toggle off to disable a visualisation from accepting any filter input.

‘Background refresh interval (minutes)’ shows how often, in minutes, the landing page refreshes the visualisation if you have navigated away from it.

‘Real time update’ updates score in real-time.

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.

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.