Skipped Records are ACL

[Prateek Tyagi]

Hi All,

I have upgrade the instance to san diego patch 7 .I have 12 skipped records . which are ACLs . Now when i Compare them with the base system they have a difference in the operation field of the ACL . In base system the operation field have the sys_id but in he customized one it is having the report_view . The sys_id is same when compared to the report_view record But in base it is having sys_id and in the customized one the name of that record. Can any one Explain ?

Thanks 

[Mark Manders · Accepted solution]

Not sure why it's showing up, because nothing really changed. I would just move them back to OOB, so they won't show up next time. I've had some of these in the past an logged a ticket with NowSupport asking them for the reason of this, but never got a useful answer.

If my answer helped you in any way, please then mark it as helpful. If it resolved the issue, please mark it as correct. This way others will find it in the solved queue and helps them on similar queries.

Mark

[Matt102]

Hi,

I'm not sure what version you came from, as I believe this issue is/was resolved in RP10+, it might have something to do with this: Report View ACL's may become inactive after family upgrades & patching (KB1121670 ).

tab,matt

[Harish Kota]

Most Probable Cause:

PRB1610243 - OOB Report View ACLs skipped during the upgrade
As part of the effort to enable Report View Access controls (RVAs) many of the Access Control Lists (ACLs) were enabled and intentionally flagged to prevent changes to out-of-the-box (OOB) RVAs during an upgrade process.
As a result, these RVAs are seen as 'skipped' during an upgrade. 
ServiceNow has introduced Report View ACLs (RVAs) as an additional layer of control on tables in inactive state.
RVA activation done through the scheduled maintenance or via ACL Assessment for Reports application creates Customer Update records to avoid an issue where upgrades may load the OOB RVA in inactive state.
These Customer Update record cause future upgrades to skip RVAs, generating Upgrade Logs with Skipped disposition.

Solution Proposed:

You can safely ignore the skipped ACL's and mark them as reviewed as needed.
No changes or modifications have been made; the logs are reporting these RVAs as skipped due to customization.
No further action besides indicating the logs have been reviewed is required.

[Community Alums]

500+ of these report_view ACLs skipped upon upgrading to Tokyo patch 2 this week. We've never touched those ACLs as its a very new instance that only went live in April and we let SN do those report view activation few months ago. Wondering why this is happening...