OBS field audit trail is not working properly
search cancel

OBS field audit trail is not working properly

book

Article ID: 279447

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Audit trail is not logging the audit data properly for the 'Changed by' and 'Date fields' on a project when the OBS field value is updated as Null. The audit values for 'Changed by' and 'Date fields' are captured as the values who updated them for the last time instead of the latest values. 

Steps to Reproduce:

  1. Login as Admin into Clarity
  2. Create a custom OBS in Clarity
  3. Create Levels and units on the above created OBS
  4. Associate project object with the OBS created in Step 2
  5. Open the project object from studio and enable auditing for the custom OBS field 
  6. Choose any project and assign any resource(except admin) as manager to the project
  7. Make sure that the above project manager has Project Management Navigate and Project Tiles Navigate access
  8. Now login as Project manager from step 6 and assign a value to the custom OBS field on project from step 6
  9. Observe the changed by and date fields on the audit trial page
  10. Now Login as admin again and update the custom OBS field as Null on the project
  11. Access the Audit trial page on the project

Expected Results: The latest audit trail entry should have the 'changed by' field as Admin and 'Date' as 'todays date' (Date and time when the field was updated). 

Actual Results: The latest audit trail entry has the 'changed by' field as the Project manager name instead of the 'Admin' and the 'Date' as the timestamp during which PM updated the OBS field.

Environment

Version: 16.1.3

Cause

DE79339

Resolution

DE79339 is fixed in v16.2.2.