PLANNED_CST_TOTAL!=PLANNED_CST_TOTAL(previous value) auto-start condition
search cancel

PLANNED_CST_TOTAL!=PLANNED_CST_TOTAL(previous value) auto-start condition

book

Article ID: 279012

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

I have created a project object-based process with an auto-start condition that checks the current project Total Cost against the previous value.

If the value changes the process should auto-start, however it does not

STEPS TO REPRODUCE:

  1. Build the following process:
  2. Object: Project 
  3. Start Option: Update
  4. Start Condition: ( Project Planned Cost != Project Planned Cost [Previous Value] )
  5. Validate the process
  6. Create a project and financially enable it
  7. Add a financial plan and provide some cost
  8. Change the Cost values

Expected Results:  The process auto-starts as the condition is met

Actual results: The process does not auto-start

Cause

This is caused by DE66277

Resolution

This fix is behind feature toggle and by default it is off (16.2.0 and above)

  1. select enabled from cmn_features where code = 'RAISE_EVENTS_ON_PLANDETAIL_UPD_DE66277'
    1. 0 means disabled
    2. 1 enabled.
  2. If an update is required:
    1. UPDATE CMN_FEATURES SET ENABLED = 1 WHERE CODE = 'RAISE_EVENTS_ON_PLANDETAIL_UPD_DE66277'
  3. restart the Clarity services or Flush the Clarity cache