Best Practices for validating impact before setting glide.angular.legacy to false

[vv303332]

Hi Everyone, 
We have Health scan recommendation to change the glide.angular.legacy system property from true to false.

I have reviewed the official documentation and understand why ServiceNow recommends disabling the legacy AngularJS behavior security reasons .However ,i couldn't  find any official guidance describing the recommended validation or regression testing approach before  enabling the change

I have a few questions:
1) What testing needs to be performed before changing the this system property to false?
2)Have you observed any functional or upgrade - related issues after disabling the property?
3)is there any official ServiceNow KB or recommended regression test checklist for this change?
4) Did you identify and validate all the custom AngularJS components(Service portal widgets, UI pages, custom client side script etc.) before making the change?

[yashkamde]

Hello @vv303332 ,

1) If talk about testing every custom widget, UI pages using Angular directives (ng-*, $scope, angular.element). So test and check browser console for Angular errors, re-run ATF suites touching Service Portal.

2) Also I haven't seen upgrade issues caused directly by changing this property. The issues that do occur are almost always related to custom AngularJS implementations that depended on the legacy behavior rather than OOTB ServiceNow functionality.

3) As far as looked up, you can check this ServiceNow Client-Side JavaScript Library Patching - Security :

AngularJS Long Term Support 

4) In short if your instance has been heavily customized over the years, I would strongly recommend performing a complete inventory and regression test first, as there is no automated way to guarantee that all legacy AngularJS dependencies have been identified.

If my response helped mark as helpful and accept the solution.