Process auto-starts even if condition is not met
search cancel

Process auto-starts even if condition is not met


Article ID: 240369


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


Custom object process always auto-starts when the condition is to auto-start on Update, when the value of a lookup custom attribute is different than the previous one, even if the value has not changed. This occurs from both the UI and from XOG, even if the attribute is not even included in the request.

Steps to Reproduce:

  1. Create a master custom object (e.g.: custom_obj). Make it Event/Copy/Export/View All Enabled.
  2. Create a custom attribute based on a lookup (e.g.: custom_attr, based on BROWSE_INV lookup). Make it Presence Required and set an API Attribute ID.
  3. Create a new process based on the custom object, with an auto-start condition of ( custom_obj custom_attr != custom_obj custom_attr [Previous Value] ), with the only step to "Finish".
  4. Create a new custom_obj instance.
  5. Set a value for the custom_attr, and Save.
  6. The process will trigger (expected, as the custom_attr value has changed).
  7. Save again.

Expected Results: The process does not trigger, as the custom_attr value has not changed.

Actual Results: The process will trigger.


Release : 15.9.3, 16.0.0, 16.0.1, 16.0.2 

Component : Clarity XOG and REST API




Targeted Fix in Release 16.0.3