ActivitySequence Behavior Inconsistent Across Various Levels (Client Level, Customer Level and Policy Level). (Doc ID 2910128.1)

Last updated on NOVEMBER 18, 2022

Applies to:

Symptoms

On : 11.2.7.0 version, General

ACTUAL BEHAVIOR
---------------
Previously, when an Activity A created Activity B via ActivitySequence with ProcessImmediate = YES,
all Activities on the target entity where activity B was created which have a lower Effective Date, or the same EffectiveDate with a lower or equal ProcessingOrder would be automatically processed before Activity B.
If one such pre-existing Activity encountered an error, Activity B would be left Pending, and Activity A would move to Activity Sequence Error Status.

Recently noticed that this behavior no longer occurs when Activity B is sent to a Client or Group Customer level entity.
The prior erroring Activities are ignored, and do not interrupt the processing.
The expected behavior does still occur if Activity B is sent to a Policy level entity instead.


EXPECTED BEHAVIOR
-----------------------
When an auto-processing Activity is sent to an entity, it will continue to behave as before, with prior Activities being processed first, and halting if prior Activities encounter an error.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create Transactions at the Client level, Customer level, and Policy level.
2. Policy, Client, Customer level Transaction1 - design this transaction to do nothing but trigger a business error 100% of the time.
2. Client, Customer Transaction 2 - design this transaction to do nothing at all, just process successfully when created.
3. Customer Transaction 3 - design this transaction to use Activity Sequences with ProcessImmediate = Yes to optionally create instances of Activity 2 on the various levels.

Policy level test: (what is expected at all levels)
1. Begin by adding Activity 1 (the error Activity) to a Policy on the first of the month.
2. Add the Customer level Activity 3 on the second of the month and fill it out to spawn and process the Policy level Activity 2 immediately on the Policy from step 1.
3. Observe that an Activity Sequence error is encountered, as expected. This is due to the inability of the prior Policy Activity 1 to reach Active Status.

Client level test: (what has changed)
1. Add Activity type 1 to a Client record on the third of the month.
2. Add the Customer level Activity 3 on the fourth of the month and fill it out to spawn and process the Client level Activity 2 immediately on the Client from step 1.
3. Observe that no Activity Sequence error is encountered, and that Client Activity 2 processed successfully despite Client activity 1 being pending still on a prior date.

Customer level test: (what has changed)
1. Add Activity type 1 (the error Activity) to a Client record on the fifth of the month.
2. Add the Customer level Activity 3 on the sixth of the month and fill it out to spawn and process the Customer level activity 2 immediately on the same Customer.
3. Observe that no Activity Sequence error is encountered, and that Customer Activity 2 processed successfully despite Customer Activity 1 being pending still on a prior date.

Cause

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