When a Hyperspace link behaves differently for different users, the difference almost always comes from security. The solution to this scenario is: standard users lack security points for the activity. The component ' s own configuration is valid, as shown by the fact that it works for some people. What differs is the user, and the activity opened by the link is protected by points that must be present in the user ' s class. Options that propose a different data source, a layout restriction or an unregistered descriptor would affect everyone equally. The recommended steps are to compare a working user with a failing one, to identify the missing points and to arrange the change through the security administrator. The organization should also confirm that granting the points is appropriate, because the activity may expose sensitive information that the user does not need for their role. The analyst should also tell the requester what was changed and when the correction takes effect, since users often assume that a repair is immediate when some changes appear only after the next load or a new sign-in.
[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