Controlling Unified Map contents and appearance
Summarize
Summary of Controlling Unified Map contents and appearance
Controlling the contents and appearance of the Unified Map in ServiceNow helps you better understand and optimize your CMDB by isolating, analyzing, and simplifying CI relationships. These controls affect only your personal view and do not impact other users. Administrators have separate settings for global configuration.
Show less
Controlling Map Content
- Set Home Node: Define a central CI (home node) to reorganize the map around it, using search or right-click on a node. The home node is visually distinct and centralizes the relationships.
- Reload Map: Refresh the map display after changes.
- Filters: Apply filters to show only relevant items. Filter precedence follows user presets, shared presets, and class profiles. The home node cannot be filtered out.
- Show/Hide Filtered Items: Dim filtered-out nodes to view them without cluttering the map.
- View CI Details: Select a CI to see comprehensive information across several panels, including group CIs which show member details.
- Relationship Details: Relationships between CIs are indicated with solid or dashed lines, arrowheads, and badges showing multiple relationships. Selecting connections reveals attributes.
- Relationship Levels: Control how many relationship layers are visible to simplify or expand the map view. Mapped application services always show all levels.
- Highlight Relationships: Hover over a CI to animate and highlight its direct connections.
- Mapped Application Services: Expand or collapse grouped service instances to explore member CIs easily.
- Timeline Visibility: Toggle the timeline display for related items linked to CIs.
- Non-operational CIs: By default, these do not appear on maps or in searches, but admins can configure visibility based on life cycle stage.
Controlling Map Appearance
- Zoom Controls: Zoom in/out via toolbox buttons, mouse scroll, or mini-map navigator.
- Align and Fit: Center the map on the home node or fit all CIs within the view, with a default maximum of 250 nodes for performance.
- Move CIs and Map: Drag individual CIs to reposition, or drag the entire map or mini-map navigator for navigation.
- Show CI Key Details: Hover over or zoom into CIs to reveal names, classes, related items, and relationship directions; badges indicate multiple related items.
- Layout Options: Choose between Vertical layout (tree structure with upstream above and downstream below, default for service instances) and Force layout (clustered nodes around the home node regardless of relationship direction).
Controlling the contents and layout of a map can greatly assist with becoming familiar with and optimizing your CMDB. You can control which elements appear on the map, isolate and analyze relationships between CIs, and simplify the map to isolate issues.
Save a map as a PDF document
In the toolbox, select the Export map icon to save the current appearance of the map as a PDF document on your local drive.
Controlling map content
| Change | Tool and actions |
|---|---|
| Specify or change the home node |
The home node is the CI that all other CIs on the map are associated with, directly or indirectly. The home node icon has a thicker border that pulsates. The map is redrawn when you specify a home node. Use either of the following methods:
Note:
Connecting lines between nodes represent relationships and references, not data flow.
|
| Reload the map after a change | Select the Reload map icon |
| Configure a filter to display only pertinent items |
Select the Filter icon
When a user applies a shared preset or a user preset, all filter settings are overridden. Filter attributes from a shared preset or a user preset that do not apply to the current map are listed in the Unused filter attributes section of the filter panel. The order of
filter-setting precedence from the various sources is as follows:
Note:
Filter settings that would filter out the home node might appear in the list. You can't, however, filter out the home node even if it meets filter settings. For more information, see Use filters to specify which nodes should appear on a map. |
| Show/hide filtered items |
Select the Show/Hide filtered items icon For more information, see Use filters to specify which nodes should appear on a map. |
| Show complete CI details |
Select a CI (CI border thickens) to display its details in the Overview, Attributes, Service instances,Related items, or Changes panel. For group CIs, such as a service instance or a dynamic CI group, the Attributes panel also shows detail cards for the CIs that are members of the group. |
| Show relationship details |
Two CIs might be connected by one or more relationships (stored in the CI Relationship [cmdb_rel_ci] table). For example, two CIs might be connected by the Runs
On::Runs, Depends On::Discovered From, and by the Owned By::Owns relationships.
|
| Set the number of relationship levels to display on the map |
Use the Levels drop-down list to specify how many relationship levels to display on the map (default 3). A low setting is useful for viewing a simplified map that shows only direct connections and for limiting the overall size of a map. A higher setting enables you to review more complex CMDB structures. When a mapped application service (service instance) CI is set as the home node, the Levels setting has no effect and all levels of relationships appear. Note:
Connecting lines between nodes represent relationships and references, not data flow. |
| Highlight the relationships between CIs |
Move to a CI to animate the connections between CIs. Connected nodes are highlighted for a few seconds. Two CIs might be connected by one or more relationships (stored in the CI Relationship [cmdb_rel_ci] table). For example, two CIs might be connected by the Runs On::Runs, Depends On::Discovered From, and by the Owned By::Owns relationships.
Note:
Connecting lines between nodes represent relationships and references, not data flow. |
| View mapped application services (service instances) |
The Service Mapping app might use mapped application services. Mapped application services appear as group CIs that you can expand to show members. Mapped application services [cmdb_ci_service_discovered] are descendents of the Service Instance [cmdb_ci_service_auto] class, such as service instances and dynamic CI groups.
|
| Show or hide the timeline | Select the Show/Hide timeline icon |
| View non-operational CIs |
An administrator can change the default behavior to show non-operational CIs or CIs of any combination of Life Cycle Stage values. For more information, see Configure CIs to appear based on life cycle stage value. |
Controlling map appearance
| Change | Tool and actions |
|---|---|
| Zoom in or out |
Use any of the following methods:
|
| Align the map to the home node | In the toolbox, select the Align to home node icon |
| Fit all CIs on the map |
Select the Fit to map icon Result: Center the map on the canvas and set the zoom level to the maximum level that enables the entire map to fit on the canvas. By default, up to 250 nodes can appear on a map. CIs in a collapsed group CI are counted. Note:
Admins set the maximum node count using the unifiedmap.map_search.max_nodes property in the workspace-specific [sn_cmdb_ws_config_property] table. Higher values can decrease performance.
|
| Move a CI to another location | Drag a CI to a different place on the map. Map elements that are connected to that CI might be moved to accommodate the new placement. |
| Move the entire map on the canvas and set the zoom level |
Use either of the following methods:
|
| Show CI key details on the map | Move to a CI to show its full name and class (or zoom into the map until those details appear), its related items details, and the direction of the CI relationships. If there are multiple related items associated with a CI, then the CI badge contains the string 'Multiple' and a badge showing the count of related items appears on the timeline. You can move to the badge on the timeline to show all related items. |
| Switch the layout of the map |
Note:
Connecting lines between nodes represent relationships and references, not data flow. |