My Oracle Support Banner

Grace Period Functionality Is Not Working As Expected For Two Or More Parallel Tasks (Doc ID 2857564.1)

Last updated on MARCH 30, 2022

Applies to:

Oracle Communications Order and Service Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Information in this document applies to any platform.

Symptoms

 Grace period functionality is not working as expected for two or more parallel tasks

Problem Description
---------------------------------------------------
We execute the following scenario:

An order is waiting in two parallel long running tasks: TaskA and TaskB, both in Accepted state.

TaskA has the compensation configuration:
 -  "When this task needs to be re-evaluated, compensate by": Do nothing
 -  "When this task is no longer required, compensate by": Do nothing
 -  "When an amendment occurs this task will be compensated if it is": Completed
 -  "When an amendment occurs if this task is in progress it will": Wait for the grace period

While TaskB has the compensation configuration:
 -  "When this task needs to be re-evaluated, compensate by": Do nothing
 -  "When this task is no longer required, compensate by": Undo
 -  "When an amendment occurs this task will be compensated if it is": Completed or in progress (Include expression: fn:true() - Complete expression: fn:false())
 -  "When an amendment occurs if this task is in progress it will": Be excluded from the grace period

While the order has both TaskA and TaskB waiting in Accepted state, a revision order is submitted (specifically a cancellation order). The target order state turns to "Amending", but the order state normally remains "In Progress" waiting for the grace period of the TaskA (Indefinitely). After a while, TaskA receives a final response message from the external system and it gets Completed.

According to the compensation plan described above, we would expect, upon TaskA completion, the amendment to start being processed immediately, the order state to be changed from "In Progress" to "Amending" and TaskB to be executed in Undo mode. However, during our tests, we observe that upon TaskA completion, the amendment is not being processed, the order state remains "In Progress" and the flow transits to the next task. It seems that the grace period option of TaskB, which should lead the task to NOT wait for the grace period, is not being considered by OSM.

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


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