Cardinality/Constraint rules not working in configurator UI with Radio Buttons (Doc ID 1298052.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM - Version 8.1.1.1 [21211] to 8.1.1.4 [21225] [Release V8]
Information in this document applies to any platform.
***Checked for relevance on 02-06-2016***

Symptoms

The radio buttons for a product relationship do not work with constraints when the "None" button is selected twice. This is happening when using the vanilla UI Control "Radio Buttons with Price JS". The problem is that the cardinality/constraint rules are not been checked after the selection of "None" when "None" option has already been selected.


The issue can be reproduced by following these steps:
1. define a new CxP with one relationship with min cardinality = 1;
2. define a new UI group, add the relationship and defined UI control = "Radio Buttons without Price JS";
3. add the Cxp to an order and click Customize button;
4. the following behaviour occurs if "None" option is clicked twice:
- if the user clicks Done button, Configurator allows to save the incomplete configuration without complaining about the cardinality broken rule;
- if the user selects another option after clicking twice None and clicks Done, the product is not added to the relationship.

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