What is the right way to identify a attribute/field requirement based on different scenarios?

MJONES_OH
Tera Expert

Hello! 

Our team is planning to build out our CMDB Health Dashboard and have run into a challenge with identifying Mandatory (Required) fields. For the purpose of the Health Dashboard, it appears this is asked to be done at a Dictionary level. However, through conversations with our dev team, we've learned there are a variety of ways to identify a field as "Mandatory" (required). Some examples are UI Policy, Data Policy, Business Rules, Dictionary, etc.. However, it doesn't appear that we understand clearly why we choose one option over another to make a field Mandatory. 

Can someone please help me understand why I would choose to make a field Mandatory through Data Policy vs. something like UI Policy, Dictionary, etc.? Looking to figure out what each option does differently from the other.

 

Mike Jones
Business Process Architect | CMDB Product Owner - ServiceNow ITSM & CMDB
The Goodyear Tire & Rubber Company
0 REPLIES 0