OSM Not Honoring Granularity For Delay Tasks Configured For A Rule At Function Level Data
(Doc ID 2822204.1)
Last updated on NOVEMBER 22, 2021
Applies to:
Oracle Communications Order and Service Management - Version 7.3.5.0.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
OSM not honoring granularity for delay tasks configured for a rule at function level data
You have a function associated to a process that has a delay task.The rule for the delay task is configured to wait on ControlData/Functions/WaitFunction/OrderItem/OrderItemRef/DueDate.
There are two order items in the order, each with different DueDates. Let says OrderItem1’s DueDate is today and OrderItem2 DueDate’s is tomorrow.
You have two instances of the wait function, each has exactly one orderItem.
The expectation is for Function1 which has OrderItem1 with DueDate1 as today will wait for DueDate today to occur and Function2 which has OrderItem2 with DueDate2 as tomorrow will wait for DueDate tomorrow to occur.
But OSM is randomly picking the DueDate from one of the OrderItem. It is not honoring the granularity of the function.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |