Risk Recalculation on CI Add/Remove from task_ci Table Not Working — Any Suggestions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2025 02:14 AM
Hi everyone,
I'm trying to implement risk recalculation in Change Management when Configuration Items (CIs) are added to or removed from the task_ci table. I’ve created a Business Rule named "Recalculate Risk on CI Add/Removed" that runs after insert and delete on the task_ci table.
The goal is to ensure that risk is recalculated not just when the cmdb_ci field is updated on the Change Request, but also when related CIs are modified via the task_ci relationship. However, the Business Rule doesn’t seem to be triggering the recalculation properly.
Client feedback also emphasized that relying solely on cmdb_ci updates is insufficient, and that risk must be recalculated when records are added or removed from task_ci.
👉 Has anyone faced this issue before or implemented a more reliable solution for this scenario?
Would love to hear if there’s a better approach or design pattern that works well for this use case.
Thanks in advance!