Set Preference Rule Not Working On Changing Promotion Level Cardinality
(Doc ID 2375422.1)
Last updated on SEPTEMBER 09, 2021
Applies to:
Siebel Product Configurator - Version 16.14 [IP2016] and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Cardinality rule not firing.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Scenario 1: Working
With above configuration Child1CP2 added to order by default when User added RootCP2 through Edit Offer.
Scenario 2: Not working
Change Promotion Level Cardinality Min: 0, Max: 1, Def: 0 (we have rule to default Product. so, Promotion level cardinalities changed to align consistency)
Rule not fired: Child product not defaulted when User added RootCP2 through Edit Offer.
Scenario 3: Not working
Reverted Promotion Level Cardinality to original State as Min: Blank, Max: blank, Def: Blank.
Rule not fired: Child product not defaulted when User added RootCP2 through Edit Offer.
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 |
Cause |
Solution |
References |