My Oracle Support Banner

Order Remain Stuck In Amending State After The Processing Of A Fallout Exception (Doc ID 2672150.1)

Last updated on JULY 16, 2020

Applies to:

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

Symptoms

OSM 7.4

  Order is stuck in Amending state

In order to reproduce the issue, please follow the workaround below:

a. build and deploy cartridge 'SimpleOrchestration'
b. create order using CreateOrder.xml which is part of cartridge
c. complete TaskA_1
d. update 'data' node with value 'd3' at TaskB_1
e. add 2 pivotNode instances at TaskB_2 and complete task
f. complete TaskB_SP_1 and TaskB_SP_2 for both instances of subprocessB_subprocess
g. trigger exception at TaskB_3 for element 'data'
h. update 'data' node with value 'd4' at TaskB_1 redo
i. remove one instance of pivotNode at TaskB_2 redo and complete task
j. complete TaskB_SP_1 undo and TaskB_SP_2 undo of subprocessB_subprocess
k. note that the order remains stuck in Amending state at TaskB_3 with do execution mode

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.