Domain Separation - Domain visibility list only if Top contains the domain?

david_legrand
Kilo Sage

I have a weird behavior on my DEVELOPER Fuji instance.

According the Domain Separation Setup - ServiceNow Wiki, I should be able to easily add a "domain contains another domain". (and it worked for me on Eureka instances if my memories are correct).

Structure:

I want to give "MSP Offshore" accesses to "Customer 1" and "Customer 4".

So I click on "edit", for the "contains domains" and I don't have any domains because the domain can't see the full hierarchy.

My workaround is:

1) On the Top domain, add "contained by" MSP Offshore (to give MSP Offshore the full access to the hierarchy)

2) On the MSP Offshore domain, go back on the "contains domains", add the necessary domains and remove the TOP domain.

But do we agree this is not how the domain separation should work on the contains domains?

1 ACCEPTED SOLUTION

david_legrand
Kilo Sage

I found the solution (I think) and I'm informing ServiceNow Hi support so the wiki will be updated.



We need to use the "Toggle Domain Scope" to use the domain of the admin (global normally) instead of the current domain.




I'm copying below the wiki page http://wiki.servicenow.com/index.php?title=Domain_Separation_Setup#Creating_Contains_Relationships_B... and highlighted in yellow, I'm adding the additional step




4.3 Creating Contains Relationships Between Domains

Creating a contains relationship between domains changes the domain hierarchy. Domains in a contains relationship inherit the visibility settings of the containing domain. The containing domain allows users to see data in the contained domain as well as any of its children. Processes are unaffected by a contains relationship.


  1. Navigate to the domain table.
  2. Select the domain record that will be the parent (container) domain of the new contains relationship.
  3. Make a right click on the "record banner" and use the menu item "Toggle Domain Scope" (new Fuji feature)
  4. From the Contains Domains related list, click Edit.
  5. Select the domain records that will be the child (contained) domains of the contains relationship.
  6. Click Save, and then click Update.
  7. You don't need to undo the domain scope, it's undone automatically once you quit the record

View solution in original post

14 REPLIES 14

Hi David,


Kindly find my earlier post. There is a system property introduced from Fuji release "glide.sys.domain.use_record_domain_for_data", changing value from true to false will do the trick.


Hi, I don't think that a good idea because if the 2 approaches were available back in the day (on Eureka, Dublin...), that was a source of mistakes for MSP agents.


Using the "record" as the source of the domain is the best approach and I guess the property should be used only if you don't have over choices (I haven't been trained on Fuji Domain Separation but I would guess that based on my understanding but maybe someone official will confirm)



Regards


That sounds good. Agree with you.


Thank you David. We are looking into the issue and will make the appropriate documentation update.


ms_akila
Mega Expert

Hi David,

 

I have some idea on this issue.

if you want to give domain contains access from MSP Offshore" accesses to "Customer 1" and "Customer 4".

 

Below are the steps:

1) Navigate to domain table.

2) Filter the domain MSP Offshore and open in new tab.

3) scroll down the domain record and you can find contains domain related list.

4) Click on New will open the sluch blucket.

5) Now if you search the domain customer1 and customer 4 .you cannot able to see if these domains are in parent level.

6) Open go to the servicenow home page tab , select the domain picker and set it to global if not already.

7) Now go to the Slush bucket page donot refresh . try to find the customer1 and customer4 domain. 

😎 You can able to add it now .

 

Regards,

Akiladevi R