A dashboard component displaying clinic throughput metrics requires row-specific threshold indicators that adjust dynamically based on clinic size. The component uses Dashboard Resources. Which configuration enables this functionality?
A.
Enable Threshold Overrides and Dynamic Thresholds in the Component Editor ' s Output Format form.
B.
Set the Summary Target Lookup Method to " Clinic-Specific " in the Data Source form.
C.
Configure the data source as Reporting Workbench and add clinic size filters.
D.
Add a slice for clinic size in the linked SlicerDicer session.
Threshold behavior is part of the component ' s output configuration. For the scenario described, the correct step is: enable Threshold Overrides and Dynamic Thresholds in the Component Editor ' s Output Format form. This places the logic where Radar expects it, in the Output Format form, and allows each row or context to be compared with an appropriate target. Selecting a different lookup method would change how targets are found, not how they are drawn, and edits to sessions or access settings are unrelated. After making the change, the developer should test the component with values below, at and above each limit and confirm that the indicators change correctly. The thresholds should be reviewed periodically with the business owners, because targets change over time and an outdated limit can mislead users into believing performance is acceptable or poor when it is not. Where several settings could plausibly be responsible, changing one at a time and retesting after each change makes it possible to learn which setting actually solved the problem, which is useful knowledge for later maintenance.
[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