Parameterized Dependent Lookup not cleared in New UX

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

There might be two lookup fields, the second one depending on the first one.

Changing the first one, a different behavior is observed, depending on the interface where the change is being done:

Classic UX - Changing the value of the first field and saving, the second field is cleared out.
New UX - Changing the value of the first field (automatically saved), the second field persists. 

Steps to Reproduce: 

1. Log in to the New UX 
2. Add the Department and Location fields to the Projects Grid or into a Blueprint 
3. Change the value of the Department 

Expected Results: The Location is dependent of the Department. Since the Department is modified, the Location should be cleared out, like in the Classic UX. 

Actual Results: The Location is not cleared out. 

Environment

Clarity PPM 15.x 

Cause

DE55737 

Resolution

DE55737 Fixed in Release 15.9.3 

• The fix for this issue also fixes the reported issues: DE65083, DE64184   

The ability to clear the field is enabled through a database toggle. 

• By default this change is behind a toggle.
• By default the clearing of dependent lookups won't happen.
• For SaaS Customers, if you want this enabled, please contact Support.  
• For On Premise Customers, you can enable the toggle using the following steps: 
  1. Run the following SQL Update statement 

     • update cmn_option_values set value = '1' where option_id = (select id from cmn_options where option_code = 'RESET_DEP_LOOKUP_VALUES')

  2. Refresh the application caches
• If the dependent lookup field is configured as a 'Required' field, clearing the value is not possible and the value will remain in the database.  

Additional Information

For more details on DE65083, DE64184:  New UX Dependent lookup not cleared when main field is changed to NULL