Allowing compliance reports to be updated as an alert action, as opposed to only via a Job schedule, would be an awesome addition to NCM's ability to automate remediation and help create a self-healing network. Our use case is a Cisco IOS bug, where sometimes sip bind commands drop out of startup config when an ISR is rebooted. We have a scheduled compliance report that runs nightly to check/remediate this, which is OK, but it could be better. If an alert was configured to update a compliance report whenever an ISR rebooted, it would instantly fix the problem with no admin intervention needed. Here's a screenshot of the menu in the alert config where this would be added next to the other NCM actions:
Top Comments