Best practices on Active/Failed/Aborted processes for Clarity Upgrade
book
Article ID: 139187
calendar_today
Updated On:
Products
Clarity PPM On PremiseClarity PPM SaaS
Issue/Introduction
When upgrading Clarity there is an warning on processes in checkinstall. Is it mandatory to delete the Aborted or Errored process instances before the upgrade? What are the recommendations?
Environment
All Supported Clarity Releases
Resolution
Best practices for Processes before Upgrade:
Make sure all your Active processes are put on Hold
Keep a note of which processes were Active so you reenable them back after a successful upgrade
Check how many processes you have in Completed and Error on the Initiated tab in Administration - Processes
Any processes you don't need in Initiated, Cancel and Abort
Then run the job Delete Process Instance - if you have many thousands then do it in monthly increments to avoid a large load on the system
Once you've performed the cleanup, you can start the upgrade
If you have a small amount of Failed or Aborted that should not typically fail a Clarity upgrade, however following the above best practices is highly recommended, specifically for Production environments.