Update Earned Value and Cost Totals job schedule and logs are missing post upgrade from v15.9.3 to v16.0.3
search cancel

Update Earned Value and Cost Totals job schedule and logs are missing post upgrade from v15.9.3 to v16.0.3

book

Article ID: 254406

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

The schedule and logs for job Update Earned Value and Cost Totals is removed from application post upgrade from v15.9.3 to v16.0.3

Steps to Reproduce: 

  1. Login to Clarity v15.9.3
  2. Navigate to Home -> Reports and Jobs -> Jobs -> Available Jobs
  3. Filter for Update Earned Value and Cost Totals
  4. Schedule few instance of the job
  5. Wait for the job to complete
  6. Navigate to Home -> Reports and Jobs -> Jobs -> Log
  7. Verify the job complete log is available
  8. Pause the jobs if required before upgrade
  9. Upgrade Clarity from v15.9.3 to v16.0.3
  10. Now Navigate to Home -> Reports and Jobs -> Jobs -> Scheduled jobs
  11. Navigate to Home -> Reports and Jobs -> Jobs -> Log

Expected Results: Job logs should be present and only job logs pertaining to Job Update Earned Value job is missing 

Actual Results: Job logs pertaining to Job Update Earned Value job is missing 

Environment

Release : 16.0.3

Cause

Upgrade from 15.9.3 to 16.0.0 is making the Update Earned Value and Cost Totals job cancelled state. In the next subsequent upgrades to 16.0.1 and 16.0.2 the same job in cancelled state is getting removed. This is because of a database procedure which executes the removal of cancelled jobs. 

Resolution

  • The CANCELLED status_code update to a scheduled Job happens whenever there is an update to the JOB definition xog file.
  • In the case of Update Earned Value and Cost Totals job, 16.0.0 version had an updated job definition. Therefore if the Job definition file is updated with some information (eg : addition of parameters, lookups, text area etc.) then it is evident that the Job definition template needs to get updated during upgrade. This makes the scheduled JOB instance obsolete as the new definition is available.
  • The functionality of job definition write during upgrade cancels all the outstanding jobs for which the definition is suppose to get updated. 

The cancelled jobs eventually get removed or purged via another job which is expected behavior.