A dashboard component fails to open a linked Hyperspace activity for certain users, despite a correct activity descriptor and Dashboard Resources as the data source. The dashboard is accessible. What is the cause?
A.
The users lack security points for the Hyperspace activity in their security class.
B.
The component ' s data source is not aligned with the SlicerDicer session.
C.
The dashboard ' s Layout form restricts non-admin interactivity.
D.
The activity descriptor is not enabled in the Chronicles master file.
The pattern here, success for some users and failure for others, directs attention to permissions. The correct diagnosis and remedy is: the users lack security points for the Hyperspace activity in their security class. The component has the right descriptor and data source, so it is configured correctly, but the destination activity has its own security requirement, and the dashboard cannot override it. Changing the data source, relaxing the layout or re-registering the descriptor would not help users who lack authorization. The developer should confirm the missing points by comparing security classes, discuss the request with the owner of the activity and, once approved, have the administrator update the class. Afterward the link should be tested again with an affected user. Because the failure message is often unhelpful, a short note beside the component that names the role needed can save users and the analytics team from avoidable confusion. It is good practice to record the cause and the correction in the component or report description, so that colleagues who meet the same symptom later can resolve it quickly without repeating the investigation.
[Reference: Cogito Fundamentals – Radar Dashboards and Components: Security for Activity Links, ===============, ]
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