Process Start condition - cannot compare current and old value of OBS.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Is there a known limitation on using a change in the OBS value to start a process?

The user requirement is:

If a project is moved into a specific OBS branch, the Branch manager should receive a notification that they have a new project to review.

Normally, we would use New OBS != Old OBS and New OBS = 'ABC'.

However, the system blanks out OBS if it is selected in Previous Attribute Value and puts it into Attribute value.

Environment

Clarity 16.x

Resolution

It is not supported to use previous value comparison for an OBS attribute.