Orders Stuck As Dependency is not Triggering
(Doc ID 2633441.1)
Last updated on FEBRUARY 18, 2020
Applies to:Oracle Communications Order and Service Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
There is a flow where an Order traverses from Component A to component B. The latter Component B has a data dependency on Component A. That dependency is supposed to be broken when a data attribute is changed.
The data change is made correctly, however the dependency is not broken and component B does not start it's execution.
The orders are not stuck to any task, but the problem is that the next functional component B is not triggered and do not starts execution.
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