Unable to Replace Role with Resource When a mandatory Attribute Exists Under the Team Object

Products

• Clarity PPM On Premise
• Clarity FedRAMP
• Clarity PPM SaaS

Issue/Introduction

Under Staffing workspace role replacement errors out when there is a mandatory attribute created under team object.

Although the source record for the Role request has a value entered on a custom, required field, performing a 'Replace' action is not successful. If the field is not marked 'Value Required' on the attribute definition in Studio, then the replacement works a expected and the value is copied into the new replacement record. For the use case when the required field is NOT filled in on the source record, the copy should still occur and the new replacement record should still get created. 

Steps to Reproduce: 

1. Login to Clarity with appropriate rights
2. Navigate to Classic UX --> Administration --> Objects and search for Team Object
3. Under Team object create an attribute of any data type and set as Value Required and also fill the API Attribute ID to ensure the attribute is available in Clarity MUX
4. Navigate to Clarity MUX  --> Staffing --> Staff  Grid
5. Now on any instance of role right click to replace any instance of role with named resource

Expected Results: The Staffing 'Replacement' action should be successful because the custom, required field has a value entered on the source record. 

Actual Results: The Staffing 'Replacement' action fails with a Toast message indicating a value is required for the required attribute.  

ERROR 2025-10-23 09:04:49,992 [http-nio-8080-exec-27] rest.validation (XXX:XXXX:XXXX-XXX-XXX-XXX-XXX:PPM_REST_API) (XXX-XXX-XXX-XXX-XXX) ExceptionInfo ::  Could not create resource. Resource name: obaStaffs. Error code: validation.requiredFieldMissing Error message: CMN-0007: Attribute 'z_mandatory_attribut' is required.
ERROR 2025-10-23 09:04:49,992 [http-nio-8080-exec-27] ppm.rest (XXX:XXXX:XXXX-XXX-XXX-XXX-XXX:PPM_REST_API) (XXX-XXX-XXX-XXX-XXX) 
com.ca.ppm.rest.exception.BadRequestException: CMN-0007: Attribute 'z_mandatory_attribut' is required.

Environment

Clarity 16.2.3, 16.3.0, 16.3.1, 16.3.2,16.3.3

Cause

DE177676

Resolution

Fixed in

• Clarity 16.4.1 
• Clarity 16.4.0 Patch 1 (16.4.0.1)
• Clarity 16.3.3 Patch 3 (16.3.3.3)

Workaround: Do not mark the attribute as a required field in Studio. Starting 16.3.1 Use a business rule in a blueprint to mark the field required to capture updates to the record.