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 AUGUST 10, 2020
Applies to:Oracle Agile PLM Framework - Version 220.127.116.11 and later
Information in this document applies to any platform.
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.
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:
- Create a Modify privilege and call it Modify Unreleased Part
- Create a criteria Unreleased Part with the following criteria:
$CURRENTREV Equal To $INTRODUCTORY_PENDINGCHANGE Or $CURRENTREV Equal To $INTRODUCTORY_NOCHANGE
- In the Modify privilege, only enable a few X,Y fields
- Create a Part and add to an ECO with Rev A
- Attach workflow to ECO
- 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!
In this Document