AmendDo Task Has Limitation To See The Latest Updated Data. (Doc ID 1965064.1)

Last updated on JANUARY 27, 2021

Applies to:

Symptoms

We are facing limitation to implement customer's requirement with OSM because Amend do task seems have only contemporary data which doesn't have consistency with current perspective.

■ Please verify below
1. View based update can guarantee data consistency in current order data but not next revision order.
2. Do[Amend do] mode’s Contemporary perspective actually same as Current Perspective. That means ‘Amend do’ _root data will be same as Redo’s Current perspective data.


■ Scenario
- COMMON
There are 3 component A, B, C
A has DebugTask / Sender / Receiver
B has Debug / RoutingTask / Sender / Receiver
C has Debug / Sender / ExtendedA / Receiver

- SCENARIO
I. Original Order
1. DebugTask is generate Data with ‘Blue’ and A Component is completed. (--> Updated with view base update)
2. B CheckDebugTask is completed and exit status is routed to go Routing task and Sender and receiver is completed
3. C DebugTask, Sender, ExtendedA tasks are completed and waiting for response in receiver task.

II. Revision Order
1. Same orchestration plan is created but C Component key is changed to C_1
2. C component undo is executed and ExtendedA updated the 'Data' with ‘Red’ and C SenderTask is completed with undo mode.
3. After undo execution is completed, forward sequence compensation is started and DebugTask is executed with Redo mode.
* Here, called the get order response in A DebugTask(Redo), wrong data in contemporary perspective.
Contemporary : ‘Blue’ History : 'Blue' Current ‘Red’

4. B compensation is started and DebugTask exit status is routed to Routing task. From routing task to B Receiver will be executed with Amend do mode.
* Here, Amend do want to check the latest updated data 'Red' but only 'Blue' is printing.

Cause

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