Conditional Required Modal Rule Fails on Status Report Canvas for Lookup Updates, Works in Grid

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

A conditional required modal business rule was configured to trigger when a custom lookup field on a Status Report is updated, it does not function as expected on the Status Report Canvas. Specifically, the target attribute's value is reset to blank within the modal, preventing a successful save. This rule, however, behaves correctly when similar interactions occur within the status report grid view. 

Steps to reproduce:

1. Open Clarity Studio Objects - Status Report.
2. Create a custom lookup attribute and link it to a default system-provided lookup (e.g., Attribute name = Custom status, Lookup name = Status Report Status). Add Display Mappings (e.g., Green - On Track, Yellow - Needs Help, Red - At Risk) and an API Attribute ID.
3. Navigate to Modern UX - Administration module and set up custom project Blueprints and edit rules.
4. Create a Rule of type "Conditional Required Modal" (e.g., Choose Target attribute as 'Custom Status' with condition: if target attribute 'not On Track' (Green display value) AND place any default attribute as required to populate, such as the Numeric lookup attribute 'Scope Status').
5. Publish the blueprint and assign it to any project where a status report is to be created.
6. Create a new Status Report and configure it to include the 'Custom Status' field. The conditional attribute 'Scope Status' is by default configured.
7. Change the target attribute 'Custom Status' from blank to 'At Risk' (Red display value). This action should trigger the Conditional Required Modal. Populate 'Scope Status' within the modal.
8. Observe the value populated for 'Custom Status' in the conditional required modal, enter a value for the conditional attribute 'Scope Status', and click save.

Expected Results:
The target attribute's display value (e.g., 'Red') is correctly populated on the conditional modal. The save action should successfully store the values for all required attributes.

Actual Results:
The target value is removed and defaults to blank, and the save action is unsuccessful in storing the entered values.

Workaround: None

Browser trace:

{
   "resourceId": "5050069",
   "httpStatus": "400",
   "errorMessage": "Could not update because there are additional required attributes cop_key_accomplish.",
   "additionalInfo": {
       "BRM_CONDITIONAL_REQUIRED_ATTRIBUTES": [
           {
               "sourceAttrCode": "customstatus",
               "sourceObjectCode": "cop_prj_statusrpt",
               "sectionId": "5082328"
           }
       ]
   },
   "errorCode": "rule.errAdditionalAttrsRequired.1"
}

Environment

Clarity Release: 16.3.2, 16.3.3

Cause

DE173989

Resolution

DE173989, is fixed in 16.4.0.

Additional Information

Rule using "Conditional Required Modal" is making listed fields required but blanking out the value entered into the Target attribute.