A dashboard ' s resource settings can limit the number of concurrent queries so that the system is protected from overload. To give administrators priority in the queue, the developer defines resource groups in IDK with priority levels assigned to roles. The dashboard resources record, stored in IDK, controls how the dashboard may draw on the available capacity, and priorities determine which requests are processed first when the system is busy. The first option is correct. The suggestion that there is no queuing, or that every user has equal access, would not satisfy the requirement. Custom code is unnecessary when the feature is supported by configuration and would be more difficult to maintain. Priority settings should be used carefully, because favoring one group lengthens the wait for others, and the organization should agree on which roles merit it. The developer should monitor the effect after the change, to be sure that ordinary users do not experience unacceptable delays and that administrators receive the service that justified the setting.
[Reference: Cogito Fundamentals – Radar Dashboards and Components: Resource Groups and Query Priority, ===============, ]
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