ServiceNow does not have an out-of-the-box way to make CI relationships mandatory using CI Class Manager or Suggested Relationships - they only provide guidance and cannot enforce rules. To implement this, the common approach is to add a visual message on the Proposed Change form (using a UI Policy or Client Script) that informs the user that the selected CI, such as a Server, must be related to an Application Service. Then, to actually enforce the rule, a Before Business Rule on the Change Request checks whether the required CI relationship exists in CMDB, and if it does not, it stops the change from being submitted and shows an error message. This combination gives users a clear visual cue and also ensures the relationship is truly mandatory.ServiceNow does not have an out-of-the-box way to make CI relationships mandatory using CI Class Manager or Suggested Relationships—they only provide guidance and cannot enforce rules. To implement this, the common approach is to add a visual message on the Proposed Change form (using a UI Policy or Client Script) that informs the user that the selected CI, such as a Server, must be related to an Application Service. Then, to actually enforce the rule, a Before Business Rule on the Change Request checks whether the required CI relationship exists in CMDB, and if it does not, it stops the change from being submitted and shows an error message. This combination gives users a clear visual cue and also ensures the relationship is truly mandatory.
