Unified Map vs Dependency Views in SOW – missing functionality

[Nicolai S]

I am struggling to understand the reasoning behind replacing Dependency Views with Unified Map in SOW.

As of now (SOW version 8.4.0), the Unified Map appears to be missing some important functionality — or really any comparable functionality — that exists in Dependency Views.

The most noticeable gap is the "Add Affected CI(s)" option (see provided screenshot). In Dependency Views, this allowed agents to quickly add CIs directly to the Affected CIs related list on the Incident, RITM, etc. they were viewing in SOW.

With Unified Map, this is what you currently have to do:

1. Open an Incident in SOW
2. Open the map via the Service, Service offering or Configuration Item field
3. Locate the correct CI(s)
4. Copy their names
5. Go back to the Incident
6. Open Related records → Affected CIs
7. Add them manually, one by one

That’s… quite a step backwards in terms of usability.

Yes, another option is to open the record in Classic UI, where Dependency Views is still (for now) available. But that’s not really a viable solution. SOW is clearly the direction forward.

So I have two questions:

1. Are there any plans to expand the functionality of Unified Map so it can actually replace Dependency Views?
Right now it feels more like a viewer than a tool.

2. If this is simply the way it's going to be from now on, has anyone found a good way to customize this?
Ideally something that allows us to bring back the Dependency Views functionality in SOW, while avoiding a large number of skipped records in future upgrades.

Any information about the roadmap or practical workarounds would be appreciated.