Conflict detection for manually added impacted Services /CIs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2023 05:04 PM
The conflict detection feature will identify any conflicts (e.g. blackout windows) configured on Application Services that are automatically brought into a change request as an impacted service/CI. For example, if there is a blackout on AppService1 and a change is raised on a server that AppService1 depends on, a conflict will be raised.
However, the feature does not raise conflicts for manually added impacted services/CIs.
Is this by design and is there a reason for this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2023 09:38 AM
I am noticing the same thing. Did you figure this out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2023 09:42 AM
As per my experience, it is by design but still have a look here
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************