When virtual attribute is referenced in start condition of a process, other processes(based on the same object) get kicked-off incorrectly in PPM

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

When a virtual attribute is referenced in the start condition of a process, other processes (based on the same object) get kicked-off incorrectly. 

Steps to Reproduce: 

1. Create a virtual attribute on the Task object. (Eg. v_status, referening status attribute from project object) 
2. Create a process based on the Task object with start condition on update event ( Task Name != Task Name [Previous Value] ), call it Process_1. Connect Start to Finish, Validate and Activate process. 
3. Create another process based on task object, with start condition on update event with virtual attribute involved. Eg. ( Task v_status = 'Rejected' ), call it Process_2. Connect Start to Finish, Validate and Activate process
4. Navigate to any Project, open a task, and update some field value other than its Name
5. Check the Processes tab to see if any processes that are initiated

Expected Result: Process_1 is not initialized, as the start condition is not met
Actual Result: Process_1 is initiated/completed

Environment

Release:
Component: PPMBPM

Cause

This issue is caused by CLRT-81697/DE31289

Resolution

After careful review by our Sustaining Engineering team, it has been this issue will not be fixed. Reference CA PPM's Customer-Reported Defect Resolution Policy for information on our defect process. 

Workaround: Use the parent object's attribute directly by linking the parent object as the linked object in the Process_2 definition. Example: Project (Task Investment) Status = 'Rejected' 
 

Additional Information

Reference KB000035837 - When you are using OBS structure in the process start condition and that structure changed, starting condition no longer works
Reference KB000017462 - Auto Start Idea Process Kicked Off when PPM project is saved on Convert even though start condition not met