Re-evaluate the code that is used in the 'Delete Process Instance' Job and fine-tune to improve performance.
It takes a fraction of the time to manually delete Process Instances through the application UI versus the scheduled job. Performance Improvements could be made in this job.
We have made several recommendations to the customer regarding the usage of this job in implementing a recurring scheduled job with parameters to minimize the processing time, however, this job still takes a long time to process compared to what can be accomplished manually through the application UI.
Steps to Reproduce:
- Look at the number of Initiated Processes with a Status of 'Done'
Admin Tool > Processes > Initiated
Filter Section : Select Status = 'Done'
Click 'Filter' button
Total Number of Initiated Processes with a 'Done' Status
Total Results: 36524 (# of process instances) Total Pages: 1827
- Schedule a 'Delete Process Instance' Job to delete all Done Process Instances
Main Application > Reports and Jobs > Jobs
Select 'Delete Projects'
Click 'Submit' to execute job immediately
Expected Result: I should see that the job completes within a reasonable amount of time compared to the time that it takes to delete multiple initiated process instances through the Clarity application user interface.
Actual Result: But instead I see that the job takes many hours to complete to process many instances.
Add an index on BPM_RUN_PROCESSES.SRC_STEP_ACTION_RESULT_ID column
Add an index on the PRTIMEENTRY.INCIDENT_INVESTMENT_ID column
This issue has been documented and is assigned to development for review. If you are experiencing this problem and the workaround above does not significantly help, please contact CA Clarity Technical Support.
Keywords: CLARITYKB, CLRT-6041, clarity8open, clarity12open