Guidance Required To Write Conditional Orchestration Plan.
(Doc ID 2137028.1)
Last updated on JANUARY 27, 2021
Applies to:Oracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.
The requirement is to read an order level EBM parameter from the decomposition rule.
Example: In an orchestration plan there are 5 components (c1,c2,c3,c4,c5) , out of which occurance of 'c4' depends on the value of a parameter (CustFlag1). This parameter is present in SalesOrderEBM at order level custom. If the value of this paramater is "Y", 'c4' will not appear on the orchestration plan, but it should appear.
1)The Problem is that one cannot fetch it from SignificantUpdate stage of c4. We tried the following scenario:
let $param := fn:root(.)//fulfillord:ProcessSalesOrderFulfillmentEBM/sord:DataArea/sord:ProcessSalesOrderFulfillment/coresalesordercust:Custom/CustFlag1/text()
But, we are seeing $param not fetching the value.
2) Also tried the following:
declare variable $inputDoc as document-node() external;
let $param := $inputDoc/GetOrder.Response/_root/messageXmlData/fulfillord:ProcessSalesOrderFulfillmentEBM/fulfillord:DataArea/fulfillord:ProcessSalesOrderFulfillment/coresalesordercust:Custom/CustFlag1/text()
What is the correct way to get it.
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