Wrong Init Value For Promotion Attrs Mapped To Same Field In Multiple Promotion Included In One Flow (Doc ID 2208435.1)

Last updated on NOVEMBER 29, 2016

Applies to:

Siebel Loyalty Engine - Version 15.5 [IP2015] and later
Information in this document applies to any platform.

Symptoms

On : 15.5 [IP2015] version, Loyalty

ACTUAL BEHAVIOR
---------------
Wrong init value for promotion attrs mapped to same field in multiple promotion included in one flow
We defined 2 promotions which have promotion attributes mapped to same field. When they were included in a promotion flow, we observed wrong init value retrieved for the attribute in second promotion.



EXPECTED BEHAVIOR
-----------------------
Txn "1-7XX7"
  P1 Got Applied.
  0 Non Qualifying. Points
  Updated Attribute. Promotion.Field.Number 1 = 100
  P2 Got Applied.
  100 Non Qualifying. Points   Updated Attribute. Promotion.Field.Number 1 = 200

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Create a loyalty program with 'Points' as its point type definition.
  Please refer to attached files: "$\20 Program & Promotion\eaiprogram.xml, Point Type.png".

2.Create a simple promotion P1 as following
  2a) Define promotion attribute "P1 Number1", mapping to "Number 1"
  2b) Define rule to assign points using this attribute and then update the attribute.
  2b1) assign points, using "P1 Number1"
  2b2) update attribute, set "P1 Number1"=100

3.Create another simple promotion P2, same pattern with P1.
  3a) Define promotion attribute "P2 Number1", mapping to "Number 1"
  3b) Define rule to assign points using this attribute and then update the attribute.
  3b1) assign points, using "P2 Number1"
  3b2) update attribute, set "P2 Number1"=200

  Please refer to "$\20 Program & Promotion\eaipromotions.xml"

4.Create a p日 motion flow with P1,P2 included, as illustrated in designer.png under “20 Program & Promotion”

5.Add a member "P1 P2", then transactions "1-7XX7", "1-7XX9"
  Please refer to "$\30 TestCase\Transaction List.csv"

6.Process the two transactions

7.Check processing log
  7.1) Txn "1-7XX7"
  P1 Got Applied.
  0 Non Qualifying. Points
  Updated Attribute. Promotion.Field.Number 1 = 100
  P2 Got Applied.
  100 Non Qualifying. Points   Updated Attribute. Promotion.Field.Number 1 = 200

  7.2) the 2nd Txn "1-7XX9"
  P1 Got Applied.
  100 Non Qualifying. Points
  Updated Attribute. Promotion.Field.Number 1 = 100
  P2 Got Applied.
  200 Non Qualifying. Points   Updated Attribute. Promotion.Field.Number 1 = 200

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms