How to domain separate existing records

[d-aizawa]

Hi.

My project has Phase1 and Phase2.

Phase1 includes incident, problem management, and change management.

Phase2 will introduce Domain Separation by implementing a new system.

Although it is still in the consideration stage, create domain A and domain B,

・Domain A：Incident, Problem, Change

・Domain B：New System

Due to the introduction, I am studying about Domain Separation, but I have the following two points that are unclear, so please let me know.

①I would like to change all the existing records to Domain A, how can I do that?

②How can I separate domains for Incident and Change Business Rules, UI Policy, Workflow, etc.?

Thank you!

[SatyakiBose]

Hello @d-aizawa 

Mapping existing records or moving existing records to specific domains in not the best approach.

Domain separation should be installed on the vanilla instance, and then you can create record, script, and other dependencies in the specific domain.

To put it in simple words:

1. When you have an active production instance, all the data is present under global scope, and it contains customer data as well.
2. Now if you install domain separation on this instance, you cannot import or move the existing customer data which are on global domain to customer-specific domains.
3. Only the data that is created post the domain separation plugin can have a domain value.
4. Multiple customers have domain-separated instances. But then the plugin is installed right when the instance was commissioned, and not mid-way when the production instance is used in full fledge.

Hope I was able to make this clear.

Now the reason ServiceNow does not recommend this is to maintain data integrity and avoid data loss and data corruption.

If you need further validation, I would recommend you to have a support case created for official documentation purpose.

Now to answer your question.

1. Not recommended to move existing global domain records to another domain post domain separation plugin being installed.
2. If you are talking about domain separating the entire table, then it is not possible. You can only domain separate records in the incident, change, business rules etc. 

[Crystal16]

I am happy to see this post as we are also facing similar issues with domain separation, and hope I can get some feedback also on our scenarios we are facing.

Currently we are using ITSM applications, e.g. Incident, Problem, Change applications in ServiceNow, with users from different countries, and we are using ACL (or business rules) currently to restrict for example China users to see only China users/groups/records etc.

In order to have data segregated to meet data access requirements, we'd like to enable Domain Separation.

However, I do have several concerns:

1. Not sure the Domain separation is a good solution for us;

2. Not sure if Domain separation can be enabled and working in running instance. And if possible, how about the workload, and complexity about the configuration / data migration etc.

3. Do we have any official documentations Question 2 - if possible to enable domain separation on running instance, and how to do that in general?

Thanks so much for anyone who could share your thoughts or experience on this question!

Apprecate all your feedback!

[Rashmi Bansal]

I am also having the same problem statement. please advise