It appears that when I migrated our instances to Platform Analytics and used their migration tool, it installed about 40 business rules titled "Track artifact creation post-migration" that SN's Impact system is now flagging as bad code. All it seems to do is update a system property called "glide.par.coreui.migration.new_coreui_artifacts_created" to "true". Impact's Scan Engine says this is bad practice to set a system property in a script. I don't see why this BR should run on any insert or update to a sys_report_source, a sys_ui_hp_cascading_filter, or a pa_m2m_dashboard_tab. Is it hurting anything? Probably not, just extra BR's to process. I'd like to clear that finding though. ServiceNow's AI keeps saying stuff about it being for tracking updates, but I don't see this doing anything like that. The property been set to 'true' and has not been updated since creation in 2024. I thought I'd throw this out to the community before opening a case. Was this supposed to be cleaned up at the end of migration processing?
The entire script:
(function executeRule(current, previous /*null when async*/) {gs.setProperty("glide.par.coreui.migration.new_coreui_artifacts_created", "true");})(current, previous);
