Clarity PPM: Project Team table last updated date appears inaccurate

Document ID : KB000109966
Last Modified Date : 14/12/2018
Show Technical Document Details
Issue:
Why is the field 'Last Updated Date' on the PRTEAM table being updated to be the time that the Time Slicing job  last updated the record?
This causes confusion to the users because they did not make any changes to the Project Team records on the date specified.
 
Cause:

If a change to allocation is made on a Project Team tab, the 'Last Updated Date' appears inaccurate.

The completion date and time of the Time Slicing job replaces the prior Last Updated Date of the time the actual user that made the change.
1. When allocation is updated, the 
PRTEAM.last_updated_date and 
PRTEAM.last_updated_by 

the timestamp is updated. 

2. When the Time Slicing job sees the change, it processes it and sets 
PRTEAM.last_updated_date to be the Time Slicing job completion time. 

So, the PRTEAM.last_updated_date is updated again 

3. Each time an update occurs, the CMN_AUDITS uses the PRTEAM.last_updated_date and 
PRTEAM.last_updated_by 

Resolution:

This defect was caused by a fix implemented in version 15.3.0.
Defect DE44708 was opened to review.The defect is now resolved in Clarity 15.6 targeted for MAY 2019.

So the change in Clarity15.6 is that when allocation is changed by the user, the PRTEAM.last_updated_date now uses the date stamp of the moment the change was made and not the Time Slicing job completion time.