Update % Complete runs for all Active investments in the system

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

On a large system, Update % complete takes 5 minutes to run. Some of the dirty tasks for templates are uncleared

On investigation, the job runs for all the active investments in the system (45K) even though there is no dirty tasks on most.

 

STEPS TO REPRODUCE:

1. Find a very large system with 45K investments
2. Update a project Task Start or Finish date to trigger the flag IS_PCT_DIRTY 
3. Run Update % Complete job with all parameters cleared
4. Note it takes 5 minutes
5. Create a copy of the same job by using the same Java class in a new custom job definition
6. Do not add the obs_unit parameter, just all the other parameters
7. Update a project Task Start or Finish date to trigger the flag IS_PCT_DIRTY 
8. Run the custom job with all parameters cleared

Expected Results: The OOTB job to run for a short amount of time as very few tasks are set to dirty

Actual Results: The OOTB job run for 5 minutes, The custom job with same class without obs_unit parameters runs in 10 sec.

Environment

Clarity 16.4.1

Cause

DE184698

Resolution

In Review with Engineering

Workaround: Use the custom job without obs_unit parameter until a fix is available