My Oracle Support Banner

Criteria $CURRENTREV Equal to $INTRODUCTORY_PENDINGCHANGE or $CURRENTREV Equal to $INTRODUCTORY_NOCHANGE Not Working to Determine Any New Unreleased Revision/Changes After Upgrade (Doc ID 2312729.1)

Last updated on SEPTEMBER 10, 2018

Applies to:

Oracle Agile PLM Framework - Version and later
Information in this document applies to any platform.


Actual Behavior

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:
  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


Upgraded from Agile 9.3.2/9.3.3 to Agile 9.3.4 and above


To view full details, 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 a vibrant support community of peers and Oracle experts.