Platform Analytics Experience FAQSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Distribute and consume Platform Analytics through data visualizations and dashboards with optional filters. Explore KPIs and receive insights into significant events in the data. The Platform Analytics experience is a unified interface for visualizing data from multiple data sources. Access it in Unified Navigation at All > Platform Analytics Step into a world of effortless insights and seamless data navigation with the Platform Analytics experience, your gateway to a more intuitive and collaborative analytical journey. Unleash the power of dynamic charts that effortlessly weave together data from diverse sources, eliminating the need to juggle multiple reports and filters. Table of Contents Platform Analytics Migration Cente TimelinesDashboard Migration FAQPlatform Analytics Migration - What is migrated?How to use Migration CenterWhat is New in XanaduPlatform Analytics Migration process in Xanadu Release Platform Analytics Experience Platform Analytics Workspace FAQWhat's New in Xanadu for Platform AnalyticsData Caching in Platform Analytics Platform Analytics Migration Center: Timelines: Washington DC, Xanadu, Yokohama, Zurich: For upgrading customers, System Admins and Analytics admins can opt-in to the CoreUI Analytics migration to Platform Analytics experienceCommunication sent to customer for deprecation in Australia Dashboard Migration FAQ: Q:Can widget reports created from indicators be filtered by an interactive filter on a PAE? Ans:If you are using new next experience dashboards - then yes - the dashboard filter will automatically apply to data visualization based on the indicator (as long as the indicator has the breakdown matching the filter). If you are using responsive dashboards - then the interactive filter is not applied to the pa widgets. To filter indicator data you should add a dashboard breakdown. Q:Can you list what roles are needed to be an admin in the Platform Analytics modules and have access to create dashboards, visualizations, migrate a set of dashboards, etc but does not give admin access to the overall platform? Ans: You can find some information on this product doc page: https://docs.servicenow.com/bundle/washingtondc-now-intelligence/page/use/par-for-workspace/reference/platform-analytics-roles.html Q: What are we supposed to use instead of dashboards and what is the difference between the dashboards and the visualizations? Ans: We have released from Tokyo the new Platform Analytics workspace/experience and that is where the migration of analytics content will go. Q: Where is the KPI Composer/Planning elements in the Platform Analytics Experience? Ans: Right now there is nothing specific to the new Platform Analytics experience. The current KPI composer in the planning phases will still work till we are in the process of rethinking about the solution for the Platform Analytics experience. Q. What type of migration is recommended?(Phased or Bulk). Ans. If you want to test with some teams the migration and the move to Platform Analytics then you can do a phased migration of just some dashboards. But keep in mind it will migrate only the dashboard and the content inside, but it will not save it in the library. The migrate reports/pa widgets/filters will not be available from the Platform Analytics visualization library list or the filter list. All customers are still going to be asked to perform the bulk migration cause that migration is the one that migrates all content. Q: Will there be any impact to our Mobile users due to migrations? Ans. No impact on Mobile user or Service Portal users, as well no impact if users have embedded charts in forms. Q: The URLs to individual dashboards seems to vary ( before and after migration). As many of our users access the dashboards directly using URL, how can we address this? Any OOB reature available to extract old vs new URLs. Ans. After bulk migration, all the URL that were going to Core UI artifacts will automatically redirect the users to the migrated version. This applies also if you have menus connected to Core UI dashboards/reports or if users have favorites. ServiceNow will automatically redirect them to the migrated version of that artifact. Q: There is not currently a dashboard grouping feature in Next Experience. So wouldn't this be lost in migration? Ans - Correct, right now it is not available in Platform Analytics Experience. We are looking now at how we can support them Q: Will there be a way to see if a dashboard has been mitigated? Example: Migrated everything viewed in last 90 days and want to confirm there are not any others that should be migrated but to not migrate it twice. Ans - Yes there will be an option to see if they are already migrated. everything that is migrated will have a link to the migrated version when you are an admin Q:How does migration work? What are the tables involved? A: Migration reads the old content, transforms it into the appropriate next experience artifact and writes them to the database, All the next experience tables are involved since we are writing to those tables, par_coreui_migration_bridge_* tables are used to track the migration. Q: How do users stop the migration/and or rollback? A: Rollbacks are handled on a case by case basis by the development team to ensure no data loss. I would not stop the mover while its running. Let it finish. If customer wants to ensure migration does not happen setting com.glide.par.coreui.migration.enabled to false will disable the start moving button in all versions and stop the activate button from WP8 Q: What are some unsupported scenarios? A: Check the link: Content not migrated or migrated in compatibility mode Q: After migration - the dashboard/landing page issues and user preferences do not work correctly. A: We do not migrate filters and recent dashboards but do migrate favourites/bookmarks. This is being reported as PRB1796348 and fixed in the Yokohama release. Q: Post migration, the scheduled reports stop working A: This is a known issue and is reported as PRB1797369 - Targeted to Zurich and PRB1792035 - Fixed in Yokohama Q: Post migration, the report owners cannot make changes their reports. A: Migrated Report data visualization do not migrate the Created by info to Owner. This is reported as PRB1754203 - Fixed in Xanadu Q:Migration Plans for classic reports to PAE from Zurich: A:The Core UI reports are not going to be removed/deleted as capabilities till we support Service Portal and the Core UI forms with reports embedded in them. Report_admins will still be able to create Core UI reports but we agree that the functionalities above should be added in the new List component we use in Platform Analytics dashboards in the future. Q: What does migration mean? A: Your existing CoreUI dashboards, reports, interactive filters, and Performance Analytics widgets are moved to the Platform Analytics Experience. You get a single set of data visualizations and unified filters for all data sources. You can access all your analytics through a unified navigation menu. If you use indicators, you get new tools to alert you of significant changes. Q: Which components get replaced? A: Reports and PA widgets are replaced with Data Visualizations, which can show data from tables, indicators, and other sources. Indicators technically stay the same but are sometimes referred to as KPIs. Interactive filters and breakdown dashboards are migrated as unified filters. Q: Where should the migration be run? A: Run and test the migration on a single, non-production instance. Evaluate the result thoroughly. If you are satisfied with the results, retrigger and finalize the migration in a production instance. You cannot move the migrated material from a non-production instance to a production instance. For the trial run, use a non-production environment that most closely resembles your production instance in terms of dashboard content. Doing so provides the most meaningful outcome to review. Be sure to run both the non-production and production instance migrations during off-peak hours. Q: Which roles are required to conduct the migration? A: The migration requires the role admin to initiate the process. If possible, conduct the migration in consultation with pa_admin, report_admin, and dashboard_admin users. Q: How can the success or failure of the migration be tracked? A: The Migration Center is specifically designed for monitoring the success or failure of migrations and all the analytics assets that are part of the migration. For each asset, you can see the status of the migration and review the logs associated with it. You can also compare migrated dashboards and source dashboards side by side. Q: What is Compatibility Mode? A: Reports and PA widgets that cannot be migrated are imported into your dashboards in Iframes. These artifacts include (but are not limited to) funnel reports, word clouds and some custom filters and custom content blocks. Dashboards with visualizations or other widgets migrated in compatibility mode take longer to load. To enable faster loading, replace this content with supported visualizations. Q: How do I navigate to my migrated content? A: In the navigation, migrated dashboards and reports are under Analytics Center > Library. All of the administration menus for Reports and Performance Analytics are moved to Analytics Administration. Q: What happens to the CoreUI dashboards and content once they are migrated? A: After migration, the status of the CoreUI dashboards is set to inactive (the active field is set to false), but they are not deleted from the instance. Q: Will the migration impact Service Portal content? A: No, the migration will not impact Service Portal content. The service portal will continue to support reports and PA widgets. Both the report admin and PA admin will still be able to create old reports and PA widgets on the portal. Q: What will not be migrated? A: Please refer to this document for a comprehensive list of what cannot be migrated based on each release. Q: Any recommended clean-up activities before the migration? A: Remove any unused dashboards and reports to ensure a streamlined process. Please take a look at this Platform Analytics academy session for more information about possible clean-up activities. Q: How many dashboards can be migrated simultaneously? A: There is no limit to the number of dashboards that can be migrated at once. The migration process runs in the background and will not disrupt any of your other processes. Q: Is it possible to select a subset of dashboards to migrate and minimize risk, such as per department? A: Yes, you can choose the option to Try with selected content. This option lets you try out the migration or split up the migration into parts. This option is meant as a temporary measure on the way to a complete migration. Q: How about other analytics artifacts, such as reports? For example, I have many reports that are consumed independently from dashboards. A: All other analytics artifacts, including reports, are migrated to data visualizations, ensuring a comprehensive transfer of data and content. Reports that are migrated in compatibility mode are also available from the Analytics Center > Library > Data Visualizations list, but they open in Report Designer, not Visualization Designer. Q: Will the migration affect specific navigation scenarios, like bookmarks or menu favorites? A: While bookmarks themselves are not migrated, if you click on a bookmark, favorite, or any link, you will be redirected automatically to the new version of the dashboard or data visualization, ensuring a seamless transition. Q: What happens to the non-responsive dashboards? A: They need to be opened first and then migrated, otherwise we cannot convert the layout Q: What are the permissions on the CoreUI content after the migration is completed? A: End users cannot edit the CoreUI content if it is migrated to a Next Experience version. They still have access to configure the compatibility mode content. Dashboard Admins can still view any CoreUI dashboards and have a link to the migrated version. Report_admins can still view and configure any CoreUI reports and have a link to the migrated version. PA_admins can still view and configure any CoreUI PA widget and have a link to the migrated version. Q: What happens to Performance Analytics admin Console, Dependency Assessment, in-form analytics, and Diagnostics? A: Performance Analytics admin Console, Dependency Assessment, and in-form analytics feature do not apply to Platform Analytics artifacts.The artifacts from the new Platform Analytics tables are not considered.Diagnostics does not consider the Platform Analytics tables. Q: What happens to Interactive Analysis? A: Interactive Analysis is available only from Core Ui Lists Q: Why does existing Content Blocks not appear, after migrating dashboards to Platform Analytics. A: Platform Analytics does not support Content Blocks. These widgets are part of the classic dashboard framework and cannot be rendered within the new Analytics Center layout. Resolution Replace Content Blocks with supported visualizations such as:Time Series, Single Score, Breakdown Widgets, or Multi-score.For static text or instructions previously shown in Content Blocks:Use HTML widgets or embed explanatory notes within a separate custom visualization using indicator-less scores or descriptions. Platform Analytics Migration - What is migrated?: Once dashboards are migrated you have forked your dashboard and have 2 versions (Migrated Dashboard and the Core UI dashboard). Any editing moving forward should be done in the platform analytics version of the dashboards. The question still stands what is happening during this migration?Please use KB1709388 to have more details. How To Use Migration Center: Please find the attached PPT: How to use Migration Center What is New in Xanadu: With Xanadu, we enhanced the migration-center application to further support the migration of core UI-specific capabilities, like: The ability to migrate filters of type CascadingThose charts that contain chart interactions like custom URL, apply-as-filter, and drill-down chart-to-chart interactivityThe pivot chart (v1) reportMultiple columns within the multilevel pivot chartShow the top X configuration on the Performance Analytics widgets breakdown typeThe indicator scorecard configuration on custom order and labelsUnconfigured Reports, PA widgets, and Interactive filtersAny dashboard background color you might have set Additionally, the Migration Center logs are updated to a consistent format and support localization. Platform Analytics Migration process in Xanadu Release: Please use the KB1709387 to see the step by step process. Platform Analytics Experience: Platform Analytics Workspace FAQ: Q: Custom columns and export features in PAE dashboards / KPI details A: Regarding the Simple List component, Variables support and excel and CSV download we are collaborating with the List team to ensure the support in the next release. Q: Multiple UI layout issues/regressions in Data Visualization of type columns in new PAE dashboards A: Raised as PRB1789445 - Working as expected.We had a recent issue with the Store dependencies and that is probably what caused it. It is now fixed and all customers should have the issue resolved. Q: Emoji encoding broken in new "Platform Analytics Experience" dashboard's title: A: Defect has been fixed recently in Yokohama, we will look into adding the fix in Xanadu compatible Store releases.Tracked via PRB1779020 Q: Hierarchical breakdown navigation options in in new PAE dashboards: A: Currently we do not support the hierarchical navigation for Breakdowns in Dashboards. The goal is that with the new Data Snapshotting model and the multi-level breakdown capabilities, from Yokohama you could enable more than 2 levels of breakdowns for indicators, and you have less of a need of the hierarchy definitions we used in the past. Q: Remove style options in new PAE dashboards "Single score" widget A:We are currently exploring how we can improve the Single score component and bring back some presentational settings.We will update as and when more updates are available. Q: Rich text elements in new PAE dashboards do not retain custom formatting: A:On the latest version of the Platform Analytics Store bundle compatible with Washington, the issue on the Rich Text component is fixed. Tracked under PRB1788262 Q: customize columns and export features in PAE dashboards / KPI details: A:We are working on supporting the option to customize the columns in KPI details during Yokohama release.We will update as and when more details are available. What's New in Xanadu for Platform Analytics: As an upgrading customer, with Washington, you got the Platform Analytics experiences there directly in the left-side menu navigation. If you haven't migrated and activated yet, this experience will be the same in Xanadu, where you still have CoreUI Reports and Performance Analytics menus available. However, new customers going in for Xanadu will see all the analytics features and capabilities solely from the Platform Analytics menu. The existing (still needed for Service Portal) Reports and Performance Analytics features have been moved under Platform Analytics Administration. There is a whole lot of features released in Xanadu. Please consume the following sway doc: What's New in Xanadu Data Caching in Platform Analytics: Starting Xanadu, Data caching can help data visualizations load faster by reusing older responses when available. Users can always get the latest data by refreshing the dashboard manually. Data caching could potentially speed up the load time of dashboards and data visualizations, especially for large datasets, for the following reasons: Caching can avoid long aggregation calculations when there have been no changes to the data.Caching can avoid aggregation calculations for users who have access to the same aggregated result data.Caching can reduce the toll on the instance from long-running requests piling up.Caching may be suitable for use cases where users are more interested in the speed with which their dashboard loads than in the freshness of the data. Please visit data-caching-pa for more information.