Custom Master Object CMO Required Fields Being Ignored?

Products

• Clarity PPM On Premise

Issue/Introduction

Steps To Reproduce

1. Create Custom Master Object
2. Create 2 String attributes
a. String attribute - test1
b. String attribute - test2
3. Access the CMO and create an instance with the attribute.
4. Make the attribute (test1) a required attribute, from the Classic.
Refresh the Modern or login/logout.
5. Go into the properties of the CMO instance and populate only text2

Expected: It should check text1 and state that field is required.
Actual: The value required field is skipped, allowing it to be blank.

Workaround: Populate text1 and then remove it, but this has to be done for instances.

Environment

16.2.0+

Resolution

This is working as designed as the validation only occurs for the current field being edited.