Widgets in Staffing still loading even if it not visible

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Large widgets may still be loading in Staffing pages even if not visible in the view and may cause slowness

STEPS TO REPRODUCE:

1. Connect to a large customer system with many resources and Staffing records
2. Go to Staffing - Allocations by Resource
3. In a default view with 3k records, click on the Show Widget icon - Manage Widgets
4. Select New Widget
   • Title: Average Remaining Availability
   • Color: Yellow
   • Type: Average
   • Widget Library - Selected
5. Save and add the Widget to the View
6. Make sure Filter Widgets is enabled, Save the view,
7. Now click Hide Widgets
8. Note : The Widget is in the View but not visible
9. Save the view again 
10. Navigate to another page in MUX
11. Now Enable Dev Tools
12. Click back on Staffing

Expected Results: The Staffing Allocations by Resource to load within a reasonable time

Actual Results: The Staffing Allocations by Resource loads slower, in Dev Tools we can see 4 requests to:
http://localhost/ppm/rest/v1/obaStaffs?_totalCount=false&avg=remainingAvailabilityCurve&fields=remainingAvailabilityCurve&filter=((investments____isActive+%3D+true)+and+(investments____investmentType+in+(%27project%27))+and+(resources____isRole+%3D+false)+and+(projects____obs_ChannelStackCell+in+((5075001),+%27UD%27))+and+(investments____workStatus+in+(%27in_queue%27,%27not_started%27,%27STARTED%27))+and+(resources____isActive+%3D+true))+and+((investments____isActive+%3D+true)+and+(investments____isTemplate+%3D+false))&limit=1&totals=1&tsvParams=(periods%3D(remainingAvailabilityCurve,months,6,2024-03-01T00:00:00,fiscal,totalsOnly)),(workEffortUnit%3Dhours)

The Widget should not have been loaded since it's hidden from the view. 

Resolution

This is DE80379, reviewed by Engineering and Product Management and it is Working by design

The widgets will load after the grid information is loaded regardless if the widget bar is collapsed or not. This is by design and has always worked this way. 

Workaround:

1. Remove highly intensive widgets completely from the regularly used Standard view
2. Create a new view with the highly intensive widget to only consult it when needed