Save button not enabled when MVL field is made required via rules

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

In the modern UX when you have an MVL (Multi-valued lookup) attribute set as required via business rules, the required field modal does not show the save button upon selecting values.  

Steps to Reproduce: 

• Create a static lookup (example: LKP1) and create some values in the lookup
• Create a MVL lookup attribute on the project (example: Field 1) and choose the static lookup created in step 1.
• Create a business rule to set Field 1 as required 
  • Example: Rule name = Rule 1
  • Rule type: View Page
  • Conditions : Always True
  • Actions: Required Attributes, select Field 1
• Create a new project from the grid or update an existing project via the properties module.
• The required fields modal page appears, select the values and try using the save button

 

Expected Results: The save button to be active soon after selecting values on the required MVL lookup field

Actual Results: The save button does not appear for a long period or at times it would never appear.

 

Environment

16.2.1, 16.2.2

Cause

DE80588

Resolution

DE80588 is fixed in upcoming release i.e.  16.2.3 (targeted in August 2024) 

Workaround: Hit the tab keyboard action to establish a focus on the save button