Configuring the dependency mapping
Overview
Starting with v. 1.2.0023 , the following areas appear after extension installation:
- Dependency Map Settings navigation item in the Master Data Application (in earlier versions, its display should be enabled from the Administration application → User Interface → Navigation Items → Dependency Map Settings navigation item)
- Show Dependency Map action (in earlier versions, its display should be enabled from the Administration application → User Interface → Actions → Show Dependency Map action)
Dependency Map Settings
The Dependency Map Settings navigation item is available in the Master Data application. Open this dialog for editing to set up which dependencies should be tracked.
General Configuration
The following options are available in the General tab of the Dependency Map Settings:
- Dependency Levels: defines the default number of the displayed Dependency Levels. The default is 3.
- Dependency Sibling Levels: defines the default number of the displayed Dependency Sibling Levels. The default is 1.
- Dependency Grouping: if checked, determines whether dependencies having the same beginnings and the same ends must be grouped into a single one with the description containing the number of dependencies grouped
- Highlight Root (since v.1.2.0023): checkbox to highlight the root and the color to be used for it; this will add a border to the node that is the root object (starting point) of the dependency map. Checkbox options:
- enabled: by default, the highlight color is enabled and is set to green (#16e34a), but it can be customized.
- disabled: uncheck the checkbox to disable the highlight entirely
To make navigation easier in large dependency maps, the root object (starting point) is now automatically highlighted when the map loads as follows:
Highlight Root helps users instantly locate the origin of the map, improving clarity and efficiency when analyzing service relationships.
Dependency Map with the Item Design set to Circle: Highlighted root item 'TCK00001 - test' and a red border for the "comp1' item with the Compliance Alert
- Show Compliance Alert (since v.1.2.0023): checkbox to show the compliance alert is selected by default; this will add a red border and exclamation mark to the nodes once a Ticket, Incident, or Service Request, regardless of its status, is associated with the CI on one of the relations SPSActivityClassIncident.Asset, SPSActivityClassIncident.AssetAffected, SPSActivityClassBase.Service or SPSActivityClassBase.ServiceAffected
- Item Design (since v.1.2.0023): can be either a circle (default) or a rectangle.
You can now switch to a Rectangle Item Design in the Dependency Map to visualize availability metrics directly on the map.
In Rectangle mode, supported assets and services show Availability Status, including Committed and Actual values. Enabled via Dependency Map Settings with optional CI-type filtering.When the Rectangle is selected, the option to Show Availability Data is enabled, and the CIs that should display this availability can be configured:
Show Availability Data configuration example
This enhancement gives IT teams and service owners immediate visibility into service health while analyzing dependencies — no need to switch contexts:
Dependency Map with the Item Design set to Rectangle: Highlighted root item 'TCK00001 - test' and a red border for the "comp1' item with the Compliance Alert
Configuring the dependency Mappings
On the Mappings tab of the dialog, there are two settings with default values:
- Allowed Configuration Items for Object Class Dependency. By default, this setting contains a list of all objects for which dependencies can be set on the Dependencies tab of the object dialog. The Show Dependency Map action will display such dependencies along with the dependencies from attribute mapping that is described below.
You can exclude an object if the action should not consider dependencies set in the dialog of the corresponding object.
- Dependency Attribute Mapping. This is a list of all relations between configuration items that are tracked by the dependency mapping. By default, they are disabled.
To enable the required dependency mappings, click a dependency mapping record from the grid to open its dialog. Select the Enabled checkbox and click Finish to save the changes.
You can also add relations to this grid. Any relation between objects in the system can be configured as a dependency.
Display
On the Display tab of the dialog, you can adjust the visual display of configuration items on the dependency map. Configure display logic and color rules per object type via Object Display Overrides, where you can define the following:
- In the Configuration Item field, select an object.
- Now you can set a specific icon for this object in the Icon field.
- In the Display Expression field, you can set a display expression that will be used to label this object on the dependency map. This allows control when and how the highlighting appears (e.g., only for active incidents or specific asset types)
- Status: enable the Show Status Color
- Color: define custom highlight colors for affected Configuration Items (CIs)
This flexibility helps avoid misleading visual cues, especially in business-critical overviews or Change Management scenarios, and allows tailoring the map visuals to suit specific operational requirements:
Adding a new dependency mapping
Any relation between objects can be set up as a dependency. To create a new dependency mapping:
- Run the Create new item action from the Dependency Attribute Mapping grid.
- In the opened dialog, select the Data Definition whose relation you want to add.
- If you select the Choose a relation from the list radio button, you will see a drop down field with relations of this data definition. Choose the appropriate relation.
- If you select the Provide expression for relation radio button, you will be able to enter an ASQL expression for the relation.
- In the Allowed Configuration Items field, select a configuration item for which this dependency mapping will be valid.
- Use the Type field to set the type of dependency. For certain types the direction of dependency can also be set.
- You can also select the layer of dependency in the corresponding field. A layer represents the level of infrastructure connected to the selected dependency.
A layer can be set only for new dependencies. All pre-defined dependencies come with the Unknown layer.
Choosing colours for dependency lines in the Show Dependency Map wizard
You can configure the color of a dependency line for different layers. To adjust colours for different layers:
- Go to the Administration application and open the Schema → Data Definition → Pickups.
- Find the Service Pickup Dependency Layer pickup.
- Open it for editing and adjust colours on the Data tab of the dialog.
As a result, the dependency lines of each layer will have the selected color.
Adding custom configuration items to the dependency mapping
To enable the dependency mapping for custom CIs, the relation between them needs to be set up from both sides.
Example
You have a custom configuration item Business Application with data definition TSTBusinessApplicationClassBase which has an attribute and a relation:
- Attribute: Name
- Relation: Host (n:m to SPSComputerClassBase)
If you want to include the business application to the dependency map for computers, you need to set up two relations:
- Relation starting from the Computer configuration item
- Relation starting from the Business Application configuration item