A Radar dashboard, enabled and Ready for Use, is not visible to a specific user group. The dashboard includes SlicerDicer-based components. What should the administrator check first?
A.
The dashboard ' s Access form for inclusion of the user group ' s Report Groups.
B.
The components ' Display Titles in the Component Editor.
C.
The SlicerDicer sessions ' data extraction to Caboodle.
D.
The dashboard ' s Owning Application for Cogito settings.
Where one group of users reports that a released dashboard is not visible, the connection between the group and the dashboard is where the cause lies. The correct action is: the dashboard ' s Access form for inclusion of the user group ' s Report Groups. Visibility is determined on the Access form through report groups and user types, and any group that is missing from it will not see the dashboard. The other options, which concern titles, data sources or ownership, do not decide who may view the content. The recommended sequence is to review the form, add the appropriate group and test the dashboard with an account from that group. The developer should also review the dashboard ' s components, because a user who can open the dashboard but not its components will have a poor experience, and every user in the audience must have the security to use all of them. 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: Dashboard Visibility and the Access Form, ===============, ]
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