My Oracle Support Banner

Wait Condition Don't Work Properly When Multiple Elements Defined As DataChangeNotificationProperty (Doc ID 2753981.1)

Last updated on FEBRUARY 26, 2021

Applies to:

Oracle Communications Order and Service Management - Version and later
Information in this document applies to any platform.


On : version

Wait Condition don't work properly when multiple elements defined as DataChangeNotificationProperty

There are 3 fulfillment patterns

- TOFP_Resource.Local_Loop.DEFAULT (FP-A)
- TOFP_Resource.Vacant_Account.DEFAULT (FP-B1)
- TOFP_Resource.AAA_Account.DEFAULT (FP-B2)

There are 2 functions

- WholeBuyFuntion (function A)
- ActivateItemFunction (function B)

FP-A participates in function A.
FP-B1 and FP-B2 participate in function B.

In FP-B1,a dependency is defined between function A (from FP-A) and function B.
In FP-B2,a dependency is defined between function A (from FP-A) and function B.
Both dependencies have wait condition defined, checking for Data Change Notification for different properties defined in Order Item Properties.
The Data Change Condition Expression XQuery in FP-B1 always gets evaluated, but the condition for FP-B2 is never resolved/evaluated




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

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