This is an overview of domain separation as it pertains to the CMDB Query Builder. Domain
separation allows you to separate data, processes, and administrative tasks into logical
groupings called domains. You can then control several aspects of this separation, including
which users can see and access data.
Domain separation is
supported in this application. Not all ServiceNow applications support domain
separation; some include limitations on the data and administrative settings that can be
domain separated. To learn more, see Application support for domain
How domain separation works in the CMDB Query Builder
With the CMDB Query Builder you can easily build complex infrastructure and service queries
that span multiple CMDB classes, and that involve many CIs that are connected by different
relationships. Domain separation is set to be on by default.
- Saved Query
The user creates a query by dragging a class node from
the class hierarchy and dropping it to the canvas and connecting the nodes with the
The user can save the created query as an XML file to the database
[qb_saved_query] table in the CMDB for future use. The saved query is domain separated.
- Query results
With a saved query, the user clicks
Run and the query result is saved and displays in the platform list
In the query results, the domain separation behaves in the same way as the
platform list view for the CI relationship [cmdb_rel_ci] table and CMDB CI [cmdb] table.
Consequently, since the CI relationship is not domain separated, all relationships of the
query result display, regardless of the domains. Conversely, if the query result is CI only,
since the CMDB CI is domain separated, the results display only if visible in the current