In this series, I'll spend roughly an hour in a Quebec PDI discussing some features in the release notes that were interesting to me. This article builds off of the knowledge found in my previous post for UI Builder. Now Experience Dashboards can only be built in the new UI Builder and will not apply to previous/legacy workspaces.
For this article, I just replicated 1-2 tabs of the out-of-the-box Incident Management dashboard that existed previously. Note: Since I'm working in a scoped app, I had to ensure I could read Incident from my app.
I want to preface this article by saying that UI Builder has a lot of depth. This post isn't an end-to-end demo on how to build a workspace and then put a dashboard inside of that workspace. More posts to come on building workspaces themselves once I learn more about navigating through UI Builder. This post will be focused more on what dashboards look like in Now Experience, and the different tools and terminology that goes along with building a dashboard within a Now Experience.
Here's what the OOTB Dashboard looks in the Platform UI:
Create a Workspace Experience
I'm going to plug the LCHH on this again, because without it I would've missed some steps on setting this up. So here's what I did:
Create Workspace Experience by clicking Create experience in Platform
On the UX Page Registries page, clicked New
Titled my UX Page Registry, Dashboard Concept, used the Agent Workspace App Shell under App Shell UI, gave it a URL path, and here's the tricky part, go into Admin Panel by clicking the magnifying glass, and chose UX App Configuration for the Table Name, and Dashboard Concept for my Document. Note: I see Workspace for Table name too, and perhaps I should be using this instead if I want to incorporate this in a Workspace, right now I'm just exploring as I go, more on this to come. I did create a UX Page Registry using it Workspace: Agent Workspace as the Admin panel, but unsure of where this goes or what connects it all together at the moment.
Create a Page
Since I'm not building out a full workspace experience for this post, I just used the Dashboard page template. I didn't plug in any parameters or anything, I also renamed this variant to Dashboard Home later on, at first it was Dashboard concept default.
I encourage you to go into your PDI with no specific goal in mind, and just create some pages using the different templates to see what they're about.
Next, I added the Dashboard viewport component to my page. When adding a Dashboard viewport, you can either add a previously created Dashboard built with Dashboard Builder, or you can create a new one.
Since I don't have any Now Experience dashboards built yet, I want to the Open Dashboard Builder link under Config to launch that window and begin building. This opens a new page called the Dashboard Builder.
The Dashboard Builder is where you'll be configuring your dashboard. You have to launch it when creating or editing your Dashboard as this cannot be done right from the Dashboard Viewport component in the UI Builder.
Dashboard Builder Toolbox
For the layout under Dashboard configuration, I just left it as standard because I knew I wanted tabs, and wanted to do my layout within tabs.
I started my Dashboard with a Tab Set component because the out-of-the-box dashboard had tabs. This was just me guessing here, but it seemed to work for what I wanted. I'm assuming Tab Sets will also be used when creating the 'Record' page of a Workspace Experience as well to provide the multi-tasking experience.
Next, I dropped a Data Visualization component in my Tab Set component. I also dropped in some Container components since I want to control the layout.
Note: Data Visualization is the new name for both the Data Visualization/Report/PA Components since Paris.
I wont go through setting up indicators and PA for every data visualization component I build. From my initial impressions, it doesn't seem like you can port existing reports over into Now Experience Dashboards like Platform UI dashboards. You either get the option to use Indicators or Tables.
I did hit some brick walls here on Performance Analytics report types such as Breakdowns, as it seems like these are not available. There is also not a 'List' report type either, I'm assuming this is meant to be replaced with the List component, but the drawback here is that you can't use Performance Analytics Indicators and display them in a list, since the List component only uses Tables. I could be wrong, but upon first glance this is what I noticed.
With the PA reporting limitations in mind, I just created some basic Data Visualizations off the Incident table for my next tab. If you want different layouts for your components make sure you use a container.
I created a new Tab for my Incident Open tab, and created a container with four cells.
Here's the finished product, if there are more dashboards available to you, you can switch by clicking the down arrow next to the dashboard title.
Incident Overview Tab:
Incident Open Tab:
You can also share from this view by clicking the Dashboard actions (three dots) icon, as well as edit the dashboard or create a new one (if you have the correct roles)
Here's what I did in this post:
Create a Workspace Experience
Create a Page with UI Builder
Create a Dashboard with Dashboard Builder
Dashboards are re-usable across different workspaces. You can add your dashboard (component) to various workspace experiences, based upon roles, etc. for both the dashboard and workspace.
Dashboard Builders will have to learn how to navigate the UI Builder. This may or may not be a positive point right away. Existing (platform UI) dashboards are somewhat user friendly for citizen developers or stakeholders to build, this will be a learning curve at first.
Previous, I'll call them legacy or Platform UI Dashboards cannot be converted. They must be rebuilt in the new UI Builder.
You can no longer create Workspaces either in Studio, or Navigating to All Workspaces > New. In the past, you could create a Workspace fairly quickly under a scoped application with all of the List/Record/Etc. pages and components created for you. As I piece together Workspace Experience, it seems like creating a full end-to-end Workspace may take more time and configuration than it did in the past. I'm assuming the logic behind this, is that agents should be using the Agent Workspace, and the Agent Workspace should be configured appropriately to limit specific agents to the data/lists/landing pages, etc. that they need, rather than creating their own Workspace for them. ServiceNow has ported over CSM Workspace, and configuration is a little different there.
There's still so much to learn about UI Builder!