My Oracle Support Banner

How to Troubleshoot Process Extensions (PX) when They Are Behaving Differently in a Standalone Agile API Application Compared to Running Them in the Agile User Interface (Doc ID 1306967.1)

Last updated on JULY 02, 2018

Applies to:

Oracle Agile PLM Framework - Version to [Release to 9.3]
Information in this document applies to any platform.


How to troubleshoot PXs that are behaving differently from a standalone developer's tool compared to running it from with in Agile.

The standalone is usually using JDeveloper or Eclipse (for example) that is connecting to the user's environment to test custom code.

Running it from with in the Agile environment is invoked by a user logged into Agile and doing some action needed to get it to run.

This is most commonly found when users are developing custom and testing it in their environment and it is getting different results in the UI.

Troubleshooting Steps

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
Troubleshooting Steps

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.