Domain separation and Service Mapping
Summarize
Summary of Domain Separation and Service Mapping
Domain separation in Service Mapping allows you to logically segment data, processes, and administrative tasks into distinct domains. This segmentation controls user access and visibility, ensuring that data is correctly assigned to the appropriate domain, which is essential for service provider use cases. The application supports domain separation at runtime, including user interface elements, caching, reporting, and aggregations.
Show less
This functionality requires setup by the instance owner to enable multi-tenant operations, making it suitable for environments where service providers manage multiple tenants securely and independently.
How Domain Separation Works in Service Mapping
- Users operate within leaf domains (domains without child domains) to perform mapping actions.
- When creating or managing service instances, the service instance and related configuration items (CIs) must belong to the user’s domain.
- Manual addition of CIs or connections requires users to be in the same domain as the application service.
- Imported service instances and groups are automatically assigned to the user’s domain.
Domain Separation and Automated Service Suggestions
Automated Service Suggestions supports domain separation starting from version 1.9.0 (not supported on-premise). Key points include:
- Source and target processes must be within the same domain to create connections.
- Users can only view data within their current domain.
- Post-installation of Service Mapping Plus with domain separation requires verification that all content is assigned to the correct domain.
Practical Implications for ServiceNow Customers
- Domain separation enables secure, multi-tenant management of service mapping data and processes.
- It ensures proper data segregation, which is critical for service providers handling multiple customers.
- Users must be aware of domain boundaries when performing service mapping tasks, including creating service instances and managing CIs.
- Automated Service Suggestions respects domain separation rules, limiting visibility and connection creation to the current domain.
Additional Resources
Customers can refer to related documentation on enabling traffic-based discovery, creating and customizing patterns, and best practices for domain separation in service provider environments to optimize their use of Service Mapping with domain separation.
Domain separation is supported in Service Mapping. 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: Basic
- Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.
- The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
- The owner of the instance must set up the application to function across multiple tenants.
Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer’s message, the customer must be able to see the SP's response.
For more information on support levels, see Application support for domain separation.
How domain separation works in Service Mapping
In domain-separated environments, switch into relevant leaf domains to access actions related to mapping performed by Service Mapping. A leaf domain is a child domain of the lowest level, meaning it does not have any child domains itself.
- When creating an service instance, the service instance is assigned to the user's domain.
- When manually adding a CI to an service instance, you can choose only CIs that belong to the service domain.
- When manually adding connections to CIs to an service instance, users must belong to the same domain as the application service.
- When transferring service definitions between instances, imported service instances and service groups are assigned to the user's domain.
Domain separation and Automated Service Suggestions
- The source and target process must reside in the same domain to create a connection.
- The user can view only the data in the current domain.
Automated Service Suggestions supports domain separation starting with version 1.9.0. No support is currently offered for on-premise instances. Reach out to product management for further information.