Project-object Portlet Performance Issue When Filtering on an ACA
search cancel

Project-object Portlet Performance Issue When Filtering on an ACA

book

Article ID: 212673

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

A portlet based on the project object's status report is not performing well due to an Aggregated calculated attribute (ACA).

Steps To Reproduce:

1. On the Project object, create an attribute called "Overall Health Status" with the following properties
Expression: AGG_Sum(cop_prj_statusrpt.cop_overall_status)
Filter: max( cop_prj_statusrpt.last_updated_date,"EQUALS",cop_prj_statusrpt.last_updated_date )

2. Create a portlet based on the project object.

ID, Name, Overall Health Status

3. Filter on the portlet on the numeric value based on the color (Overall Health Status):
90 : RED
50 : YELLOW
0   : GREEN

Expected: The portlet returns results within 10 seconds. 
Actual: The portlet takes 2 to 4 minutes to return a couple of records matching.

Environment

Release : 15.8.1

Component : CA PPM STUDIO

Cause

The number of projects and its status reports has to be evaluated and the above filter condition will take time.

 

Resolution

Since the ACA can introduce a performance issue based on a large number of projects and its status reports, consider the filter condition being used.

If it performs poorly, consider designing a process workflow to optimize the performance.

Additional Information