Mandatory attributes are not honored in the property page in MUX

Products

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

Issue/Introduction

Steps to Reproduce: 

1. Login to Clarity with Administration rights
2. Create a mandatory attribute at Project/Investment Object with API attribute ID
3. Now copy a standard project blueprint and create a new custom project blueprint
4. Add those mandatory attributes to the properties module under a section and publish it
5. Use any existing projects and update the blueprint of few projects to newly created blueprint
6. Now open any of the projects and fill any other attribute and data gets saved even though mandatory attribute is blank

Expected Results: A pop up on the UI asking user to fill the mandatory fields 

Actual Results: Data gets saved without filling the mandatory attributes 

Environment

Clarity All Versions 

Resolution

This This is Working as Designed 

The only time the MUX forces the user to enter a value on a Studio-enabled required field is at the time the record is created. The MUX does not have a 'Save' button to go through and validate all fields on the page for an EXISTING record, therefore any Studio-enabled required fields are not processed when the user updates any other field on the page. (It is assumed the record was created with a value for the Studio-enabled required field). The same behavior occurs on the grid during the update of another field.  In Studio, when a Required attribute is created or an existing attribute is updated to be enabled as a Required field and there are EXISTING records on that object, the Administrator can populate all existing records with a value using the 'Populate Null Values with the Default' option. If the Administrator wants to leave this field blank on EXISTING records, then the management of the field can be done through MUX Business Rules or left up to the individual users that own the instance data.