Processes are starting when start conditions are being not met post 16.1 upgrade
search cancel

Processes are starting when start conditions are being not met post 16.1 upgrade

book

Article ID: 255563

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

In 16.1.0 it is reported that the process on an investment, that uses "Previous Value" in start condition, will get invoked when any of the following changes are made to the financial plan record within that investment. Processes will be invoked even if the process conditions are not met.

  1. A new cost plan is created as a plan of record
  2. Any change made to the plan of record Cost Plan
  3. A budget plan is approved
  4. A benefit plan that’s associated with a cost plan (plan of record) is updated.

Steps to Reproduce: 

  1. Create process based on idea object with below start conditions
    1. Start Condition for Create
      ( ( ( ( ( ( ( Idea Idea Type = 'Basic' ) or ( Idea Idea Type = 'My Cust Type 1' ) ) or ( Idea Idea Type = 'My Cust Type 3' ) ) or ( Idea Idea Type = 'My Cust Type 4' ) ) or ( Idea Idea Type = 'My Cust Type 5' ) ) or ( Idea Idea Type = 'My Cust Type 6' ) ) or ( Idea Idea Type = 'My Cust Type 7' ) )
    2. Start Condition for Update
      ( Idea Idea Type != Idea Idea Type [Previous Value] )
      Note: Issue is observed with previous value comparison in the start condition.
  2. Connect start to finish step and validate process.
  3. In studio for Idea object set default for Idea Type attribute to 'Basic' or any other value.
  4. Financially enable idea with Location and Department values.
  5. Create Cost Plan on the idea and go to Details.
  6. Click on Populate from Allocations action.
  7. Observe process created in Step 1 got trigerred even though Idea Type value never changed.

Expected Results: Process should not trigger

Actual Results: Process is triggering.

Environment

Release : 16.1.0

Resolution

DE67632, fixed in 16.1.1, 16.1.0.1