Required Attribute Rules on Modern UX Trigger even when the attributes have values but not present on Properties Module.

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

If there are attributes which are required with the use of Business Rules and they are not configured on the properties/details module, the rules keeps triggering even when the required attributes have values. 

STEPS TO REPRODUCE:
1. Login to Classic UI.
2. Navigate to Administration -> Studio -> Objects -> Project object.
3. Create a Test Attribute of String type. Provide an API alias to it.
4. Navigate to Modern UX -> Administration -> Blueprints.
5. Create a copy of the standard blueprint and create a new rule as below.
    -> Rule Type :- View Page 
    -> Conditions (Always True) :- false
    -> Match Filters :- Work Status == TRUE
    -> Actions :- Required Attributes - Test Attribute
6. Create a project and assign this blueprint.
7. Populate the Test Attribute with a value and set the Work status to Active.
8. Navigate to the Properties/Details tab on the project.
9. Update the description field.

Expected Results: Since the required attribute has a value, it shouldn't pop up.
Actual Results: The required attribute modal shows and the previous value of the attribute is not displayed. 

Environment

Clarity PPM 16.x

Cause

DE176723

Resolution

This is fixed in 16.4.1

Additional Information

Workaround :- Configuring the attribute on the Properties/Details module.