Servicenow Domain Separation Relationships

[Deepak Ingale1]

Can any1 explain me in detailed what is "contains" , "visibility" ,relationship with respect to domain separation.

I know contain is the relationship defined between domain to domain but how does it work?? . Does it reverse the parent child hierarchy? I have gone through the wiki but did not find real world examples for this.

Also provide me info on how does "visibility" setting work "user / group to domain relationship" ? What does it indicates. How does it works? etc...

[lars_b_lund]

Hi Deepak,

Contains establishes relationships other than parent/child.

If a user/group/role should access a domain outside the parent/child defined.

When you design scope of use for the domains you do it by use of:

- domain parent/child,

- contains setting and the

- visibility setting

Visibility settings is setup by combining:

- Visibility Domain

- Managed Domain

- Sys_overrides

- Contains

I think that the visibility for a user/group/role consists of the sum defined in the 4 elements

hope you find this useful

[Deepak Ingale1]

Hello Lars,

Many thanks for this info.

In a parent-child relationship, processes are inherited by the child domain. Parent domain has access to data of the child domain as well. Correct me if I am wrong.

If it is true, does it mean that child domain also has access to data of Parent? I think it is not.

So let us say that I have two domains in a parent-child relationship, Lets say A is parent and B is child.

So if Domain B has to have access to domain A Data, do we apply relationship of "CONAINTS"? i.e B contains A ???

[lars_b_lund]

Hi Deepak

the general princip is that

- process works down from where they are defined ("until override"). Process defined i A works i B, process i B don't work i A

- data is visible from bottom and up, if data is in a given domain it is visible in the parent domain. Data defined i A is visible i B, data i A is not visible to B.

if you need access to data in a domain that isn't available in your domain or a child (or chiles-child) domain you can setup contain of that domain to grant access

in the situation you describe; if users i domain B needs to see data i Domain A you can setup that B contains A

I do hope that this is helpful

[Deepak Ingale1]

Thank you Lars, it cleared my doubts.