MUX- Auto-start condition not working on update to Total Cost
search cancel

MUX- Auto-start condition not working on update to Total Cost

book

Article ID: 275311

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

MUX- When the auto-start condition for a process is set to an update on Total Cost, it does not auto-start when the Total Cost is updated for a Cost Plan which is not Plan of Record

STEPS TO REPRODUCE:

1. Create a new project or use an existing one.
2. Create a cost plan.
3. Create a new process based on the Cost Plan object.
4. The process should auto-start based on the following condition:
Start Event: Update / Start Condition: ( Cost Plan Total Cost != Cost Plan Total Cost [Previous Value] )
5. In MUX Open the project cost plan and manually Cost in the plan detail

Expected Results: The process auto-starts. Audit Trail logs an update if it has been configured to do so.
Actual Results: The process does not auto-start. Audit Trail logs an update if it has been configured to do so.

Note: In Classic it works as expected

Cause

This is caused by DE78129

Resolution

  1. This is addressed in 16.2.1 where it requires a feature toggle to be enabled.
  2. Run the command on Clarity server:
    admin toggle-feature RAISE_EVENTS_ON_PLANDETAIL_UPD_DE66277 1