Product Configurator Constraints Does Not Fire With Attribute Default Value
Last updated on MARCH 02, 2017
Applies to:Siebel eConfigurator - Version 184.108.40.206 SIA  and later
Information in this document applies to any platform.
***Checked for relevance on 19-Dec-2011***
Constraint based on attribute value aa does not fire if
(i) aa is the default value
(ii) aa is not selected by the user but comes from defaulting
given product structure
attribute ATTR text, freeform, default = aa
Relationship R1 with
When the attribute ATTR = aa excludes selection of [CHILD B from R1]
1) hit validate -> CHILD A and CHILD B are shown in black.
Now CHILD B is shown in red.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms