Clarity UX performance degrades when Virtual attributes are included in ODF
search cancel

Clarity UX performance degrades when Virtual attributes are included in ODF


Article ID: 218603


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


Performance in the Modern UX degrades when the environment has derived, virtual attributes configured from the Team or Task objects.  

We do not yet support setting the API Attribute ID on 'Virtual' attributes in Studio, but this does not matter. Just having the defined attribute will cause issues with the performance in the Modern UX because the ODF query still generates for the entire object

STEPS TO REPRODUCE (for two use cases): 

  1. In Classic, Administration, Studio, Create some new 'Virtual' attributes on the 'Team' and 'Task' objects that come from the Project Object  (No API Attribute ID needed on the 'virtual' attribute for the issue to occur) 

  2.  Go to the Modern UX

  3. Use Case #1 - for Tasks
    Navigate to any project and go to the tasks module and open the task grid 
    Select any row on the grid and the DETAILS fly-out opens on the right side 
    Now select another task row on the grid 
    Notice the details panel of the newly selected row 

  4. Use Case #2 - for Staff 
    Open a project and go to the Staff module 
    Click the plus sign to add a resource 
    Now go to the Role field, it will hang here for up to 15 - 20 seconds 
    The yellow banner (indicating it is still being saved, takes a while to turn white) 

Expected Results: Performance for the Tasks and Staff should be reasonable. 

Actual Results: The performance is noticeably slow. 

Workaround: Remove the derived attribute from the object. 


Clarity Release 15.9.2


This is due to clarity defect DE61433.


Engineering team has reviewed the defect and determined the change has to be done via a feature work


Additional Information

Staffing page is extremely slow in MUX