How do you domain separate an existing application?

[___miked___]

I have an application that was developed from scratch using all user-defined tables that aren't extended from any other ServiceNow tables.   It basically leverages the power of the platform but none of the existing tables.   Now, I want to set it up so that different (potential) customers can access it and use it to manage their own data.   Their data has to remain private to them.   Can't leak across domains or be visible by other customers.   I initially thought I could control this by using the Domain ID field, so I added it to every table.   Not sure this is the best approach.   Am hoping that someone who has done this before can share some insights.   Will the domain field (and ACL rules) do the trick, or do I need to duplicate data tables for each domain.

[Goran WitchDoc · Accepted solution]

Hi Mike,

I haven't done this but just going to give my thoughts on it. All tables are global, even in a domain separated instance. it's the records within that is tagged with the domain id and normally you will only see the records that is within the same domain as the logged in user. So this should be the thing. You shouldn't need to duplicate data tables etc, since that would be unmanageable with a bigger application or organisation.

Make sure when you add the the field, it doesn't start with u_. Then it wont work: Domain separation administration

[___miked___]

Thank you Goran. I really appreciate your thoughts. I was hoping the Domain ID field was sufficient. I'll double check to make sure the Domain field name doesn't start with "u-."     Thanks for that tip too.