Which scenario requires a scripted Breakdown Mapping?

A scripted breakdown mapping is required when the logic to associate a record from an indicator source with a breakdown element is too complex for a standard field-to-field mapping. This occurs when there is no direct relationship or when the value must be derived or calculated. For example, mapping an incident to an age bucket requires a script to calculate the age and determine the correct bucket, as no single field on the incident record directly represents this.

B. Mapping to a Sys ID is a standard configuration. You map a reference field on the source table to the sysid field on the breakdown source.

C. Database views are supported as indicator sources, and standard field mappings can be used if the required field is present in the view.

D. Dot-walking to a related field is a standard, non-scripted feature of breakdown mappings, allowing you to map fields from related tables.

- ServiceNow Product Documentation, "Create a breakdown mapping." Performance Analytics and Reporting. This document states, "If no direct mapping between the indicator source and the breakdown source is available, create a scripted mapping."

- ServiceNow Performance Analytics (PA) Fundamentals Courseware, Module: "Breakdowns," Section: "Breakdown Mappings." The course explains that scripts are the solution for complex mapping logic where direct field or dot-walked mappings are insufficient.