Value Required attribute not honored in Classic List Page

Products

• Clarity PPM SaaS

Issue/Introduction

When an attribute is marked as value required on Studio Objects (Classic) it is not honored on the associated object's list page.

For example, an attribute that is value required on the project object still allows a field on the project list page to be edited/saved even when this value required field is not populated.

 

STR:

 

1. Create an attribute on the project object - does not matter if string or lookup type

   - Make this field Value Required

   

2. In Classic, add this field to the project list page (field will be blank)

 

3. Edit one of the other fields on the project list page and save  

 

Expected Result:  Error message stating the required field needs to be populated

 

Actual Result:  Record is saved without the required field being populated

Resolution

Reported as DE181583.  After review, it is determined this is working as designed since the implementation of MUX.  The functionality works the same in Classic and MUX.  Only records that were actually updated are checked for the required attributes.  Instances not being updated are not being checked to make sure the required attributes are populated.