Domain separation and Service Graph Connectors
Domain separation is supported for Service Graph Connectors. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
Support level: Standard*
The support level is Standard but has some exceptions or special conditions.
- Includes all aspects of Basic level support.
- Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
- The instance owner must be able to configure minimum viable product (MVP) business logic and data parameters. This configuration is done per tenant, as expected for the specific application.
Sample use case: An admin must be able to make comments required when a record closes for one tenant, but not for another.
For more information on support levels, see Application support for domain separation.
How domain separation works in Service Graph Connectors
Domain separation is supported only for multi-instance Service Graph Connectors.
You must install the Domain Support - Domain Extensions Installer (com.glide.domain.msp_extensions.installer) plugin before working with the Service Graph Connectors tables. See Request domain separation.
Tables that do not have a Domain (sys_domain) column are not domain-separated. You can add a Domain (sys_domain) column to an existing table. See Add a domain field to a table.
- The import set tables are not domain-separated.
- Transform histories are not domain-separated.
- The Key Value [cmdb_key_value] and Software Instance [cmdb_software_instance] tables, which are related to the Configuration Management Database (CMDB), are not domain-separated.
For more information about domain separation for Service Graph Connectors, see the Service Graph Connector Domain Separation article in the Now Support Knowledge Base.