Last updated on MARCH 08, 2017
Applies to:Oracle Configurator - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Display Conditions have been setup to display a User interface (UI) element only if a Text Feature
has a non-null value and such conditions are supposed to get satisfied (and the UI elements displayed) only if the Text feature has a value in it.
This is not what observed in R12.1. These display conditions always get satisfied and the UI elements always get displayed, irrespective of whether the
Text Features (on which the “IsNot null” conditions are based) have values or not.
This is not the expected or the correct behavior and this is not the behavior in 11i instances.
If the UI element already happen to have an Enabled condition, removing the condition and replacing it with a Display condition (as an “IsNot null” condition on a Text feature),then it works fine.
The Enabled conditions also have the same problem (when they have been defined as an “IsNot null” on Text features), so this problem is not just specific to Display conditions.
Display a UI element only if a Text Feature has a non-null value and such conditions are supposed to get satisfied
(and the UI elements are supposed to get displayed) only if the Text feature has a value in it.
The issue can be reproduced at will with the following steps:
1. Create a test Model
2. Add a Text Feature in this model (call it “Dummy Text”)
3. Create a Sub Tab UI for this model
4. Add any UI element in this Sub Tab UI that is applicable for Display/Enabled conditions (for example Standard Button).
5. Add a Display condition to the UI element to display it only if the “Dummy Text” has a non-null value (see below)
6. Test this UI. The UI element is supposed to get displayed only if the “Dummy Text” text feature has a value, but you will see that it is getting displayed always.
7. As an additional step, they can also try out having just an Enabled Condition on this UI element (that has been defined the same
i.e. “Dummy Text.Value IsNot null”) and test this UI and verify that the feature is enabled always (and that the Enabled condition does not work properly).
8. Now, if they go to the UI and remove the Enabled condition and switch it with the same Display condition (“Dummy Text.Value IsNot null”) and test the UI,
then it starts working properly (which is quite strange and interesting).
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