Auto update impact based on affected ci

[Debasis Pati]

Hello All,
I want to update the impact of the incident but below are the conditions.
whenever a incident is created affected ci related list is updated and the affected ci's environment is production & there is a field called business criticality is defined then i have some mappings for impact for example if standard impact is low like that according to the mapping i should map it.
now the below .
now if the incident has multiple affected ci's then the highest business criticality should derive the impact and impact should be updated also the below
also this auto updating of the impact only should happen once also if the impact we are deriving its less than the current impact of the incident it should not update.

@Ankur Bawiskar any suggestions how we can achieve this kind of scenarios?

[Dr Atul G- LNG]

Hi @Debasis Pati 

Technically, it might be a possible solution, but it’s not a good use case from a process perspective. If you want to drive the Impact field on the Incident form based on the affected CIs, the logic becomes complex and introduces technical debt. You would first need to retrieve all affected CIs, then build an array to evaluate the criticality of each one, compare them, and select the highest value.

Also, if the primary CI on the Incident already has a high business criticality, what is the purpose of recalculating the impact based on the affected CIs?

[Debasis Pati]

Yes also have a challenge that it should update once if it is earlier updated it should not trigger.Also if for this i should create a business rule then on task_ci should be the trigger table and what should be the conditions. Little confused on this actually.