Allocation and Availability audit is showing last_updated_by, last_updated_date which is confusing for any indirect changes that occur such as updating resource's calendar.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Allocation and Availability audit is showing last_updated_by, last_updated_date which is confusing for any indirect changes that occur such as updating resource's calendar.

STEPS TO REPRODUCE: 

1. Add Availability attribute on the resource object to Audit for changes, updates, delete and inserts.
2. Add Allocation attribute on the team object to Audit for changes, updates, delete and inserts.
3. Allocate some resource to 1 or more projects.
4. You should at least have 2 actors here: One is Admin which would be adding resource to the team on the project and second user who will be updating Resource's calendar.
5. After resource was added to the team navigate to Home->Resources and attempt to update resource's calendar. Note the time update was made.
6. Execute Time Slicing job. Note the time it was executed.
7. Check the Audit trail for Availability and notice that last_updated_by would the the user who made direct changes to the resource and whose id was last recorded in the srm_resources table. Last_Updated_date would be the time slicing job last run date and time.
8. Check the Audit trail for Allocation notice that last_updated_by would the the user who that made a direct change to the team (prteam table) and it will also set Last_Updated_Date to the last time slicing run date and time.

Expected Results: Customer was expecting to see the person who made changes to the Calendar to appear in the Audit.

Actual Results: It is showing last person who made direct changes to the record.

Resolution

DE77357, After Engineering team's review this is working as designed, and as of now no near plans to change the Audit capture working.
When the user 1 making the changes from the Calendar, and when we run or the scheduled Time Slicing Job is run, the data in PRJ_RESOURCES will be updated with the availability value but the Time Slicing Job will not update the last_updated_by (so the previous data for this field will be remain as last user that made the change). So the Audit will consider the last_updated_by which is available in PRJ_RESOURCES.