Independent' and 'Dependent' Identification rule?

[Mark Wood]

Hello Experts,

Could someone please explain in simple terms the use of Independent and Dependent in identification rules? I've read the documents, but I'm still not understanding them properly.

Thank you.

[AshishKM]

Hi @Mark Wood , 

In simple term it's basis of relationship type that how two CIs are related.

Example: An application installed over a window server, so application is dependent upon that server but server itself an identity and not depend upon any other CI.

https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...

-Thanks,

AshishKM

[Ashok Sasidhara]

Hope the following explanation is helpful and simple enough:

1. Independent Identification Rules: These are meant for CIs which can exist on their own (E.g. Servers, Network devices). In this case, the CI's own attributes are sufficient to identify and there is no dependency on another CI class. For example, a Server getting identified by its Serial Number or Name.

2. Dependent Identification Rules: These are meant for CIs which are dependent on another CI class and can never exist on their own. E.g. Virtual machines which need physical hosts or applications which need a server for hosting. In this case, the identification will be based on both the unique attributes of that CI class as well as the CI class which it is dependent on.

[Amitoj Wadhera]

Hello @Mark Wood ,

Of course! Let's simplify the concepts of "Independent" and "Dependent" identification rules in ServiceNow using everyday scenarios:

1. **Independent Identification Rule**:
- Imagine you have a box of toys, and each toy has a unique sticker with a number on it. If you want to identify each toy, you can simply look at the number on its sticker. Each toy's number is like its own independent ID. You don't need anything else to figure out which toy is which. That's what an independent identification rule is like in ServiceNow.
- Example: In a database of students, each student has a unique student ID number. So, you can create an independent identification rule that says, "Each student record is uniquely identified by their student ID number."

2. **Dependent Identification Rule**:
- Now, imagine you have a group of friends, and you want to tell them apart by their names and ages. Some names might be common, so you need more information to make sure you're talking about the right person. If you know their names and ages together, you can be sure who's who. This combination of information helps you uniquely identify each friend. That's what a dependent identification rule is like in ServiceNow.
- Example: In a database of customers, just knowing someone's first name might not be enough to tell them apart, because many people might have the same first name. But if you combine their first name, last name, and date of birth, you can uniquely identify each customer. So, you create dependent identification rules that say, "Each customer record is uniquely identified by their first name, last name, and date of birth combined."

In simpler terms, independent identification rules rely only on information within the record itself (like a toy's sticker number), while dependent identification rules use additional information or a combination of attributes to uniquely identify records (like knowing both a friend's name and age).

If you find my response helpful, please consider marking it as the 'Accepted Solution' and giving it a 'Helpful' rating. Your feedback not only supports the community but also encourages me to continue providing valuable assistance.

Thanks,

Amitoj Wadhera