On the Weekly Detail or other resource portlets in Clarity, the query takes a huge amount of time to return results. You may also see users are having trouble getting to or unable to access the portlet or tab. The performance degrades as the data volume increases. This happens when the user has instance or OBS Level access to a larger number of resources. You may also see an issue where results never return, the page spins, and eventually, you receive an error 500. Monitoring developer tools, the action is in pending status and may time out after about 5 minutes.
Other areas this may be reported:
Expected Result: To display results in a reasonable time regardless of the security access granted to the user.
Actual Result: It takes a long time to display results or never returns results. Performance degrades as the number of instances increases granted to the user access.
The intention of the design and use of these portlets is for a Resource Manager having access to a limited number of resources in the system for managing the planning aspect of investment work. It is not intended for use as a reporting tool, please use a reporting tool or the data warehouse.
Component: Clarity Resource Management
As referenced in the Resource Management section in techdocs, configuring a user with Instance or OBS Unit access for a larger number of resources may impact the performance of these portlets. There are a few configuration changes that can be implemented that will help to improve the performance for these portlets. You can implement some or all configuration ideas.
Note this configuration change will allow the user to view all resources in the system. In extreme cases where a resource manager manages a large portion of the user base the use of global rights might be considered. Warning: Granting of global rights can cause other performance issues when aggregation rows are added to the portlets.
When navigating to the page with the portlet and to reduce the amount of data returned in the results, the 'Show All' button can be removed in the Filter section by configuring at least one filter attribute as a 'Required' field.
The field that is configured as 'Required' can be any available field. When a 'Required' field is configured as a visible attribute in the Filter Section, it will ask for a default value. Once the field has been configured and saved, this becomes the system default filter criteria and you will no longer see the 'Show All' button. Be sure to 'Publish' this configuration change. NOTE: Publishing this change will erase any user-saved configurations or filters.
End users can create a custom default filter that returns a smaller subset of records.