A dashboard component ' s colored indicators fail to reflect department-specific thresholds for a table of quality metrics. The component uses Dashboard Resources. Where should the analyst make adjustments?
A.
Enable Department-Specific Threshold Overrides in the Component Editor ' s Output Format form.
B.
Update the Summary Target Lookup Method to " Department " in the Data Source form.
C.
Reconfigure the SlicerDicer session to include department slices.
D.
Assign department-level security points in the dashboard ' s Access form.
Threshold indicators are configured in the Output Format form of the Component Editor, and the type of override determines how the colors respond. For this scenario the correct configuration is: enable Department-Specific Threshold Overrides in the Component Editor ' s Output Format form. A single threshold set for the whole table cannot represent targets that differ by row, user, department or other context, so overrides are used to define the limits for each case. The other options place the change in the wrong object: the lookup method in the data source form decides how targets are obtained and not how indicators appear, a rebuilt SlicerDicer session changes grouping, and security points in the Access form do not affect colors. The developer should list the targets that apply, enter them in the override settings and test values on each side of every limit. Documenting where the limits are maintained makes later updates easier, and the colors should be chosen so that status is not conveyed by color alone.
[Reference: Cogito Fundamentals – Radar Dashboards and Components: Threshold Indicators in Components, ===============, ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit