My Oracle Support Banner

Product Configurator Constraints Does Not Fire With Attribute Default Value (Doc ID 1134736.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel eConfigurator - Version 8.0.0.2 SIA [20412] and later
Information in this document applies to any platform.
***Checked for relevance on 19-Dec-2011***


Symptoms


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

PARENT PROD
   attribute ATTR text, freeform, default = aa
   Relationship R1 with
                  CHILD A
                  CHILD B
Constraint
When the attribute ATTR = aa excludes selection of [CHILD B from R1]


Behavior:
1) hit validate -> CHILD A and CHILD B are shown in black.

Q: Why is CHILD B not shown in red?
2) Change attribute ATTR to 11 and then back to aa.
Now CHILD B is shown in red.
Q: Why is CHILD B now shown in red?

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


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.