Tag Policy Run finding compliant and non-compliant counts not updating
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2024 03:49 PM
The compliant and non-compliant CI counts aren't consistently being updated in the Tag Policy Run table.
It seems the Update Compliance Count business rule (https://someinstance.service-now.com/now/nav/ui/classic/params/target/sys_script.do%3Fsys_id%3D226fa...) isn't working as expected.
There are a number of runs that don't have any compliant or non-compliant CIs showing in the Tag Policy Run table
Yet there are compliant and non-compliant CIs in the related Tag Policy Run Findings table:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-29-2024 07:14 AM
Hi @William44 ,
When you fail an indicator Task, it sets the Control to "Non-Compliant" and create an Issue Task.
The Issue Task needs to be worked on.
The idea is that you need to Remediate or Accept the reason why its not compliant (in order words fix or accept the issue). If you Remediate and Close the issue, the control will change to compliant. However if you Accept and Close the issue, the control stays at non-compliant.
The "failing" indicator task was closed, it likely created an "issue" for the control. Navigate back to the control and look at the issue related list. You should see an open issue. The issue has to be closed in order for the control's status to be updated.
Refer the below Docs, which may help you.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thanks
AJ
Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/
ServiceNow Community Rising Star 2024