Wrong Application Module Instance Used in Bounded Task Flows With Isolated Transactions And No Data Control Sharing
Last updated on AUGUST 04, 2016
Applies to:Oracle JDeveloper - Version 220.127.116.11.0 to 18.104.22.168.0 [Release Oracle11g]
Information in this document applies to any platform.
Bounded Task Flow with isolated transaction ("Begin new transaction" TF option), and without the share Data control option activated use the wrong AM instance, therefore, losing already set binding parameters, etc.
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