Clarity PPM: Required Attribute Not Showing As Required in Modern UX
Article ID: 115183
Clarity PPM On PremiseClarity PPM SaaS
A project object attribute is set as required in the Classic UI, however when adding it to the Modern UX, the behavior to notify the user of a missing required attribute is not displayed.
Steps To Reproduce: 1. Create subobject on the project object 2. Create 3 custom attributes and set as required 3. Enable the subobject for API and associate API ids to the attributes 4. Add the subobject to the MUX blueprint 5. Set blueprint to a project 6. Open the project > subobject 7. Open the column configuration as well as the details and pull in those attributes
Actual Results: None of the custom attributes are marked as required A record can be created without the required custom attributes
Expected Results: A record should not be able to be created without providing the required custom attributes.
This is working as designed. The Modern UX does not contain views like the Classic UI so configuration in the views will not be shown on the Modern UX.