Project audit module records show the insert operation occurring after update of same attribute.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

SUMMARY: Project audit module records show the insert operation occurring after update of same project record for attribute when sorted ascending on Object and descending on Changed Date. Insert always occurs before update of same record.

STEPS TO REPRODUCE: 

1. In Studio enable audit for project object.
2. Add Alignment and Architectural Fit for changes and insert/delete operation and click Save.
3. In Studio enable audit for status object object.
4. Add several attributes such as Key Accomplishment, Latest, Report Date, Report Status, Schedule Status, Scope Status, Investment Manager etc.. for changes and insert/delete operation and click Save.
5. Mark one of the projects as template and ensure Alignment and Architectural Fit have data in the template.
6. Go to Status tab and populate and publish at least 1 status report in Final status and 1 draft and ensure the attributes in the audit above have some data.
7. Navigate to MUX->Projects.
8. Click on New from Template and select template from step 3.
9. Populate required fields and click on Create.
10. Once project is created check Audit module, if not visible ensure to modify blueprint to add Audit module.
11. Check Audit and you will see 2 blank rows with Insert operation and 2 with an Update operation with New Values present as per what is in the template.
12. Insert operation always occurs before update of same record whether sorted ascending or descending on Changed Date.

Expected Results: When sorting descending customer expects to see updates followed by inserts operations.

Actual Results: Insert always occurs before update of same record.

Resolution

DE79597, Engineering team looked into this defect and they think that the behavior in the defect is as per the database behavior. Reason for that is, since the new project is created from template and all the insert of attributes (in any case template/without) and update of attributes happens in the background, few inserts and updates are happening almost at the very same time. No difference at the milli/micro/nano seconds. Because of this, the database could not properly identify which record needs to be put first when sorted on "CREATED_DATE".