Criteria $CURRENTREV Equal To $INTRODUCTORY_PENDINGCHANGE Or $CURRENTREV Equal To $INTRODUCTORY_NOCHANGE Not Working To Determine Any New Unreleased Revision/Changes

(Doc ID 2312729.1)

Last updated on NOVEMBER 17, 2017

Applies to:

Oracle Agile Product Collaboration - Version 9.3.6.0 and later
Information in this document applies to any platform.

Symptoms

Criteria $CURRENTREV Equal To $INTRODUCTORY_PENDINGCHANGE or the $CURRENTREV Equal To $INTRODUCTORY_NOCHANGE as it is not working in Agile 9.3.6 but worked in Agile 9.3.2.

Need the criteria to determine any new unreleased revisions/changes and need certain fields enabled.

EXPECTED BEHAVIOR
Expect this workflow criteria to work the same as it did in Agile 9.3.2

The issue can be reproduced at will with the following steps:

1) Create a Modify privilege and call it Modify Unreleased Part
2) Create a criteria Unreleased Part with the following criteria:
$CURRENTREV Equal To $INTRODUCTORY_PENDINGCHANGE Or $CURRENTREV Equal To $INTRODUCTORY_NOCHANGE
3) In the Modify privilege, only enable a few X,Y fields
4) Create a Part and add to an ECO with Rev A
5) Attach workflow to ECO
6) See if the X,Y fields are enabled

Changes

 Upgraded to Agile 9.3.6 from Agile 9.3.2

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms