search cancel

Cost Plans - Process Start Condition set to "Update" is not working


Article ID: 213236


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


A process has been created to update certain specific cost plan information, when an update happens to it. This is done via a Process linked to the Cost Plan. However, we notice the following behaviour:

1. Have more than one Cost Plan against a Project
2. Change Plan of Record (POR) from one Cost Plan to another
3. Process triggers against the Cost Plan that becomes the POR newly
4. Process does not get triggered against the Cost Plan that was formerly a POR


Latest version tested against: 15.9.1


The behaviour here is as per current designs. The action of unmarking a Cost Plan that was a POR does not generate an Update event. And hence Processes waiting for an Update event on Cost Plan records do not get triggered. This can be observed by looking at the "Events" tab of the "Process Engines" page.