how to exclude ci attributes from creating unauthorized change request
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
if we use business rules for excluding fields from change creation how ci.unplanned.change event is triggered?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @somareddyv ,
ci.unplanned.change event is triggered independently of Change record creation. Even if custom Business Rules exclude certain fields from creating or associating a Change, the event can still fire because unplanned change detection is based on CI updates, not on whether a Change request exists.
When a CI is updated, ServiceNow’s OOTB CMDB and Change governance logic evaluates whether the update represents an unplanned change. If the update bypasses approved Change control, the platform queues the ci.unplanned.change event using its internal detection rules. This evaluation occurs outside of custom Change creation logic, which is why suppressing Change creation alone does not prevent the event.
Recommendation:
To control or prevent this event, review and adjust the CI attribute detection rules /change impact configuration to exclude non-impacting fields, rather than relying solely on Business Rules that stop Change creation. This ensures governance remains intact while avoiding false unplanned-change events.
If this response helps in solving your issue, please mark it as Accepted Solution and Helpful.
