MUX - Hidden Sections Show Incorrectly When a Hidden Attribute selection is changed.
search cancel

MUX - Hidden Sections Show Incorrectly When a Hidden Attribute selection is changed.

book

Article ID: 279801

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

After we upgraded to 16.2.0 on a custom object, we have a blueprint set up where if you don’t have the ‘Use Level 1’ checkbox selected two sections ‘Level 1 Details’ and ‘Level 2 Details’ should hide.

There is another checkbox ‘Use Resource Lookup’ which when checked hides an attribute called ‘String Value’ and shows an attribute ‘Resource Value’.  Unchecked, it hides ‘Resource Value’ and shows ‘String Value’.

On initial load, the screen shows properly.  The Level 1 and Level 2 details sections are hidden.  However, if you select (or de-select) the “Use Resource Lookup” checkbox, the hidden sections appear even though the “Use Level 1” Checkbox is not selected.  If you refresh, the sections hide again.

Steps to Reproduce: 

1. Create custom master object and API enable it.
2. Create several fields as below to be used when building sections and rules in MUX.
a. Attribute Name = Level 1 Field
   Attribute ID = lev1
   Data Type = String
b. Attribute Name = Level 2 Field
   Attribute ID = lev2
   Data Type = String
c. Attribute Name = Resource Lookup
   Attribute ID = res_loop
   Data Type =     Lookup - String
d. Attribute Name = String Value
   Attribute ID = str_v
   Data Type =     String
e. Attribute Name = Use Level 1
   Attribute ID = c_user_l1
   Data Type =     Boolean
f. Attribute Name = Use Level 2
   Attribute ID = c_user_l2
   Data Type =     Boolean
g. Attribute Name = Use Resource Lookup
   Attribute ID = c_use_l
   Data Type =     Boolean
3. Navigate to MUX->Administration->Blueprints and create 4 Rules as below and details in the attached document:
   a. Hide Level 1
   a. Hide Level 2
   a. Hide Resource Value
   a. Hide String Value
4. Navigate to MUX->Custom Objects
5. Create new instance of the custom object and set it to the blueprint defined in step 3.
6. Attempt to update values that should trigger various rules defined in step 3 and notice the behaviour where rules are not being honored randomly.

Expected Results: The Level 1 and Level 2 details sections would hide according to the business rules that indicate if the “Use Level 1” box is not selected, both should not display and if the “Use Level 1” box is selected and “Use Level 2” is not, then only Level 1 Details displays.  If both “Use Level 1” and “Use Level 2” are selected, then both sections display.

Actual Results: Each rule should be working as defined.

Environment

16.2.0, 16.2.1

Resolution

DE79770, Fixed in 16.2.2.