


- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
In this Platform Analytics Academy session, we explored the advantages of transitioning from CoreUI Analytics to a single unified Analytics Experience. We dove into enhanced features, streamlined processes, and improved data visualization. Embrace this evolution for better decision-making and deeper insights. Watch this session to elevate your analytical journey during the "Move Analytics Content from CoreUI to Next Experience" Platform Analytics Academy.
Don't let this pivotal opportunity pass by. Position yourself at the vanguard of Analytics Excellence. Check out this recorded session to understand the transformative potential of a Unified Analytics Experience. Harness its power to produce superior analytics and ensure an unmatched end-user experience. Elevate your professional journey with us.
Key Takeaways:
- Understand the challenges of fragmented analytics platforms and how unification addresses them.
- Experience a live demo showcasing the intuitive nature and enhanced features of Unified Analytics.
- Hear from industry experts on how this shift can transform your business intelligence endeavors.
Typed Questions from the Academy Session
- This may be a silly question, but is Performance Analytics and Platform Analytics one in the same?
Answer - Platform Analytics is a general term that includes Performance Analytics, Reporting, and Usage Analytics. And see the so-called Platform Analytics Experience as that new experience all under one roof analytics. Performance Analytics within that PAE is still there, but as capability, there we more talk about indicators/KPI as the data source. Using that data source triggers all your analytics capabilities within the data visualizations. As well as you will also have other Performance Analytics type of capabilities in PAE, like KPI details, KPI signals, proactive Insights, and many more. - After an item is "migrated" will a copy remain in the original UI?
Answer - yes, but marked as inactive - If you do the 'Selected Content' can you use this to only take 'Official' Dashboards and then basically 'lose' Personal dashboards?
Answer - Admins can select which dashboard to migrate, there is distinctions like ‘official’ or ‘personal’ dashboard - Does this mean all existing dashboards will need to be migrated to Platform Analytics by Yokohama or they will be moved automatically with the Y release?
Answer - Yes, so we are giving you 2 releases to do it before we do it automatically. This is better for you to do as you can use this as an opportunity to clean up what you have before migrating and also get folks used to the new interfaces and ways of doing things before it is forced. Use the 2 releases to ease into it 🙂 - Follow-up question - is Agent Workspace (configurable workspaces) required to be on Platform Analytics?
Answer - No, Agent WS or any type of Workspace will ‘live’ next to the Platform Analytics Experience. But can of course have many integrated embedded analytics within (depending on how it’s built out of the box or how you might modify those Workspaces). - What would happen to non-migrated dashboards? Would they be deleted or just not visible to users?
Answer - They will be invisible to users admins can still view them if needed. Nothing is deleted. - Will there be a new version of admin console?
Answer - In the end Yes. We are thinking of improved UIs around the admin persona for maintenance and governance. Will not be in with this switch to Platform Analytics Experience. The existing admin console will still be available through the current way. - Does the visualization designer allow for the joining of tables for more extensible reports?
Answer - The capabilities of visualizing table data are similar to classic, you can have multiple data sets, and you can dot-walk for your metrics/filter. But if you need to join tables in a more complex way admin would still need to create a DB view first before a user can use it for data visualization. - Today, interactive filters require *admin roles (report_admin or hp_publisher_admin). Content blocks require *admin (content_admin). Are there any plans to bring those elements in line with data visualizations?
Answer - Unified filters at a dashboard can be created by any user in the next experience analytics, reusable filters would require a special role (new role, customers can give it to any user). Content block (rich text/headers) - also can be created by any user. - I have heard that the underlying table structure where indicator scores, etc are stored will be changing. Can you say more about that?
Answer - Yes, but is a separate initiative. Not part of the switch to Platform Analytics Experience. But yes, we are working on a future-proof scalable, high-performance data model for analytics data. This solution will also solve current problems around the limitation of the number of breakdowns. More info on this for X and Y (safe harbor), be on the lookout for when we present something we call a ‘ new analytical model’. - If we are not currently on Agent Workspace (configurable workspaces), will migrating dashboards to Platform Analytics first make it easier to migrate to Agent Workspace?
Answer - Is not related. The only thing that will be easier - in case if you want to expose dashboards in Agent Workspace directly, then migrating them first is important, as only next experience dashboards can be exposed in workspaces. - I understand that Breakdowns and Interactive Filters will be 'merged' during the migration. How will this be impacted if there are multiple interactive filters or breakdowns for the same source?
Answer - For visualizations based on table - nothing changes - all filters will apply. As for visualizations based on indicator - in case you have multiple interactive filters/breakdowns on the page that apply to the same indicator (indicator has corresponding breakdowns) - then only the first 2 filters selected by the user will be applied to data viz and next will be shown as not applied. - Will we be able to control who can create/modify indicators once we're in the new workspace?
Answer - Yes. The creation and editing of indicators do not change at all. Only the visualization. part is changing. - Sorry joined late; are we looking at Washington in this demo? Yokohama?
Answer - This is available in Washington, opt-in users can migrate. - Can you tell from the URL if you are on a core UI dashboard vs the Next UI dashboard?
Answer - You can't understand it from the URL because after enabling the next experience if you keep some coreui dashboards they will open inside Platform Analytics. - Let me make sure I understand, all dashboards, reports etc. will need to be migrated?
Answer - Yes, everything needs to be migrated to the new experience and will be done by default in Y. We are giving you 2 releases to do it on your own, to become familiar with the new way of doing things and you can also use this as an opportunity to clean-up anything you do not need anymore. - I'm currently on Utah. What do I need to add in order to see the migration tool and start playing with things?
Answer - For the activation/migration tool that’s unfortunately not possible (it will be there as of W). But of course, you will have the option to get familiar with the new experiences (like that visualization designer, or the new dashboards). As they’re in Utah part of what we back then called the Platform Analytics Workspace. So to add, many of the new tools/features are already there on U. But we haven't marketed heavily as we didn’t have a way for you to get your content there. See the T, U, V time frame as perfect for just checking out, getting familiar, etc, with that experience. Maybe create a new dashboard there, or a new data-visualization (based on reporting or indicator data, or any of the other data sources). But we would never say ‘go recreate all your reports and dashboards’, therefor we have this migration. - I am accustomed to starting with "Indicator sources" in the navigation menu, proceeding to "automated indicators", then to "Widgets" when building my PA solutions. Will this change?
Answer - Yes, a little bit, the concept is still the same but it is all contained on one page now, you just navigate on the panel on the side to do everything instead of bouncing between different pages. You do both reporting and PA the same way now, so everything is unified and simplified, but something new to learn. - If you have multiple environments... is there a way to 'port' the migration, or would you run the migration on each environment?
Answer - The recommendation is to run migration on the instance. - If we migrate dashboards to the Next Experience will me need to migrate them again when we move to Agent Workspace or does migrating them to Next take care of this step?
Answer - No, not necessary. The new dashboard will by default be part of the Platform Analytics Experience, but you can set per dashboard to also make that specific dashboard part of another Workspace, for example, Agent WS. If done the same dashboard can also be surfaced within the dashboard UI of Agent WS. - When selecting a dashboard and clicking to migrate it, does ServiceNow then create specific data visualizations within the dashboard itself? What happens if there are 5 dashboards using a common report today, does the migration create a library visualization or is it repeated 5 individual times for each dashboard?
Answer - On migration reports inside dashboards are also migrated to visualizations and shared between dashboards. Migration creates a library visualization. - In terms of "clean up" is there an easy way to spot the dashboards that haven't been viewed in a long time?
Answer - Our next Academy session in two weeks is going to talk through some of these things: https://www.servicenow.com/community/performance-analytics-blog/platform-analytics-academy-nov-15th-... - Will report_on and report_view ACLs still behave the same in Next experience?
Answer - yes, they will still apply the same as today - Will there be enablement-based material provided ahead of the Washington release so that customers and partners can make additional preparations and prepare internal materials?
Answer - Yes! We will probably do a specific Platform Academy session on enablement material. But indeed, the plan is to deliver a huge enablement toolkit (prob on Communities) with a ton of info on the new features (for you to utilize within some enablement you might do within your company), faq, best practices, a glossary, technical documentation around the migration tool etc. - If the Dash and report on it did not migrate correctly, do you recommend first trying to fix it rather than reverting back?
Answer - Yes if you have small configuration fixes, you can edit the dashboard or report manually and that is perfectly fine. - Does the migration tool continue to enhance release by release? Ex: In 'W' it may not convert all the classic widgets to the next experience. Let's say only 70% on avg will be converted. By the next releases, those % will improve?
Answer - Yes, the migration tool itself will also keep improving. But that doesn’t mean you have to wait, some charts that weren’t in before will then within that release still migrate into the new. Added, do know that for some charts (that we now have low usage or are not good practices in general) we might choose not to bring a new version at all. In that case, the current one can still be in compatibility mode, or we might work on something to migrate it into a better chart. Eg. a pyramid chart can also be visualized as a bar chart, and would probably be a better practice as a pyramid is super hard to ‘read’. - As of today is there a possibility to view the usage and users of particular dashboards?
Answer - Come to the November 15th Academy and we will cover some housekeeping items, and while we can’t show that directly, we have a bunch of reports that can help you decide what to clear out! - Where is the timetable for these releases? Is the schedule on the ServiceNow website?
Answer - We don’t have exact dates upfront, but ServiceNOw releasing 2 times per year Q1 (GA around March) and Q3 (GA around September). So you can expect W release - Q1 2024, X release - in Q3 2024, Y in Q1 2025
Click here for previous Platform Analytics Academy sessions.
- 2,742 Views
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.