Explicit Compatibility Rule Table Selections Not Driving Selections of Second Option Class As Expected
(Doc ID 2460159.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Configurator Developer - Version 12.1.3 and later
Information in this document applies to any platform.
When making selections in a configured model, an Explicit Compatability Table rule was created in order to define one to one relationships between two option classes. Following an existing design pattern, it's noticed that in some options and models making selections in one option class do not automatically make the explicitly compatible selection in the other option class.
With the 1:1 setup of explicit compatibility it's expected that when making a selection in the first option class, the second option class will automatically select the matching option based on the rule definition.
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