Idea ID: 2769393

There should be a possibility to restrict the depth of impact analysis

Status : Waiting for Votes
Waiting for Votes
See status update history
over 1 year ago


I created an impact rule for Business Applications (BA) via use links:
BA1 -> uses relationship -> BA2


The whole tree looks like:
BA1 -> BA2 -> BA3 -> BA4 -> BA5 -> BAx


So I have a lot of connected BAs but I would like that the impact Analysis stops after the first level (so only BA1 -> BA2 is affected and the rest is untouched).
At the moment this isn’t possible with UCMDB.



Reference: OCTIM19U763144 - 'Depth of Impact Analysis'


  • not sure if I got it completely and also I did not test it...what about adding a 0..0 cardinality to a parent BA so that the impact rule will only fire on BAs having child BAs and at the same time no parent BA?

  • Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team
  • Hi Petko,

    thanks a lot for the idea. It is not 100% what I wanted to have but it is at least working for now

    BR, Manuel

  • The impact analysis rules are one of the most flexible features in UCMDB. You can control all the parameters of the impact analysis depth. How to do it:

    When you "define impacted" in the Impact Analysis Manager, you can control when the rule to be triggering and what to be the "severity relative to trigger severity". For example if you have a host which is impacted with "Critical (10)" severity. If the relative severity is reduced to 50%, then the impacted CI will have "Minor (5)" state after 1 step. After one more step, it would be "Warning (2)". On third step it would be "Warning (1)", etc. 

    Also you can define the conditions when the impact will be triggered. If you want the impact assessment to stop after 1 step, then just define Operator "greater than or equal"  to "Minor (6). Then the rule will be used only with depth of 1 and the rest will stay untouched.


    Petko Popadiyski

    Freelance Microfocus CMS UCMDB Consulting