A dashboard component fails to open a linked Hyperspace activity for some users, despite a valid activity descriptor. The component uses Dashboard Resources. 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 misaligned with the SlicerDicer session.
C.
The dashboard ' s Layout form restricts interactivity.
D.
The activity descriptor is not enabled in Chronicles.
A link to a Hyperspace activity works only for people who are permitted to open that activity. When administrators succeed and other users fail despite a valid descriptor, the difference is security. The correct explanation is: the users lack security points for the Hyperspace activity in their security class. The descriptor tells Radar which activity to launch, but it does not grant the right to use it, so each user ' s security class must include the necessary points. The other options look at the data source, the layout or the registration of the descriptor, none of which would produce a failure that affects only some users. The developer should compare the security class of a user who can open the link with that of one who cannot, identify the missing points and ask the security administrator to add them if the audience is meant to have the access. If the activity should not be available to everyone, the dashboard ' s audience should be narrowed instead. This follows the principle that every user of a dashboard must be able to use every component on it.
[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