Legacy Role Decommissioning When Core UI Reporting and Performance Analytics are fully decommission

[ajayvemula1]

We were previously on the Yokohama release and recently upgraded to the Australia release. As part of the upgrade, we enabled the recommended system properties to retain access to the Performance Analytics module, because our organization is not yet ready to complete the migration from Performance Analytics to Platform Analytics.

For future upgrades, we do not want to delay the migration from Performance Analytics to Platform Analytics. However, we need clarification regarding the impact on existing reporting and analytics roles.

Legacy role decommissioning

When Core UI Reporting and Performance Analytics are fully decommissioned, will the associated legacy roles, such as report_user, report_admin, dashboard_admin, pa_power_user, and pa_admin, also be retired?

If these legacy roles are removed, what will happen to the Platform Analytics roles that are currently inherited through them, such as:

• viz_creator
• viz_admin
• analytics_filter_admin

Will these Platform Analytics roles continue to be assigned independently, or will ServiceNow introduce an alternative role-assignment and inheritance model?

Based on our current analysis, migrating from Performance Analytics to Platform Analytics does not immediately remove the legacy roles from the instance. The legacy roles currently act as parent roles, and users assigned those roles automatically receive the associated child roles through role inheritance. However, we need confirmation on whether this role-inheritance model will remain supported after Core UI Reporting and Performance Analytics are fully decommissioned.