User Selection Is Not Saved for Config Attributes That Are Set by Two Rules
Last updated on JUNE 21, 2016
Applies to:Oracle BigMachines CPQ Cloud Service - Version 2015 R2 and later
Information in this document applies to any platform.
When any instance of an array-type attribute is set and forced-set by two recommendation rules, the user selected value of the attribute is not saved.
The behavior of the attribute when a user saves it is that of a set type.
This only occurs if one of the rule's set type is "Set" and the other is "Forced Set".
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