Processes are not triggering when start condition is based on the linked parent object on create event.
search cancel

Processes are not triggering when start condition is based on the linked parent object on create event.

book

Article ID: 384414

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

You have some processes that are not triggering for custom subobjects when expected and those start conditions are based on the attribute coming from investment parent object on create event.

Steps to Reproduce:
 
1. Create subobject of the investment object and event enable it.
2. Create custom attribute on the investment object based on the lookup "Idea and Project Type"
3. Create Master object and event enable it.
4. Create another attribute on the investment object based on the out of the box lookup which gets created when custom master object is created. This will allow for linking in the process.
5. Create a process as below:
a. Object = subobject created in step 1 above
b. Link to investment object via Parent attribute
c. Link to Master object based on the attribute created in step 4 above.
d. Start Condition 
Start Event: Create and Update
Do not start a new process if one is already running
Start Condition for Create ( Investment (Inv Sub Test Parent) Cust Project Type = 'Major Project' )
Start Condition for Update ( ( Investment (Inv Sub Test Parent) Cust Project Type = 'Application Change' ) or ( Investment (Inv Sub Test Parent) Cust Project Type = 'Infrastructure Deployment' ) )
e. Connect Start to Finish and validate and activate the process.
6. Update one of the projects values for customer attribute created in Step 2 to "Major Project"
7. Go into project properties and navigate to subobject link that was created in Step 1 above.
8. Create an instance of the subobject.
Expected Results: it is expected that process instance will be triggered.
 
Actual Results: process instance is not triggered.

Environment

16.3.0

Resolution

DE157379, Fixed in 16.3.2.