Updating task via XOG does not refresh Last Updated By

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Updating a task lookup value via XOG does not update the Last Updated By value for the task, causing processes auto-starting in unexpected circumstances.

Steps to Reproduce:

1. Create a new static Lookup with three values (Not Completed [id=1], Completed [id=2], Cancelled [id=3]).
2. Create a new lookup attribute in the Task object using the previously created lookup.
3. Create a new resource with all rights (e.g.: 'First Last').
4. Create a new process:
   • Task is primary object
   • Auto-start condition is Update, ( ( ( Task Milestone = 1 ) and ( Task Test Lookup != Task Test Lookup [Previous Value] ) ) and ( Task Last Updated By != 'Last, First' ) )
   • The process does nothing (it just finishes).
5. Create a new project with a milestone task.
6. While logged in with 'admin', update the lookup value of the task to 'Not Completed'. Check that the Last Updated By is now 'CA PPM Administrator'. Delete any process instances for this task if there are any.
7. Modify the task lookup value using XOG to Completed [id=2], logged in as admin.

Expected and Actual Results: The Last Updated By for the task is 'CA PPM Administrator'. The process triggers ([...] and ( Task Last Updated By != 'Last, First' ).

8. Still using 'admin', revert the lookup value to Not Completed using the UI. Delete all process instances for this task.
9. Do the same modification via XOG as in Step 7, but logged as 'First Last'.

Expected Results: The Last Updated By for the task is 'First Last'. The process does not trigger. 

Actual Results: The Last Updated By for the task is still 'CA PPM Administrator'. The process triggers ([...] and ( Task Last Updated By != 'Last, First' )). 

Environment

Release : 15.9.1, 16.0.0, 16.0.1, 16.0.2 

Component : Clarity XOG and REST API

Cause

DE64851 

Workaround: Redesign the process to use a different start condition. 

Resolution

Targeted Fix in Release 16.0.3