welcome everybody to the first next experience Academy that I'm going to be trying to lead here today we're going to talk about workspaces and Brad is going to be doing the majority of the talking here um check out this awesome slide with our names on them nice to meet you I'm Maria Gabriel Ocho prospector I have been a servicenow developer for six years and I just recently joined servicenow in January I am a senior outbound product manager working on next experience and theme Builders so if you like to talk about theming I like to talk about theming too yeah and my name is Brad Tilton I am also on the outbound PM team for next experience and other products and yeah excited about today's Academy awesome so some quick housekeeping real quick the chat is going to be super Lively I hope as we all chat with each other and ask questions and engage so make sure you use the Q a feature to ask questions it's going to help us keep everything in order and help us keep the answers all aligned uh use the chat for comments q a for questions the sessions being recorded the slides in the videos will be made available afterwards in our next experience uh Academy Community post yep so ask questions that you really want answered through q a and then Heckle us through the chat I think that's how it works yeah that sounds about right um so these sessions are for you ask questions and interact try to stop Brad let's see what happens if you can Stomp Them I'll give you a cookie uh this is not just a lot of cookies this is not just a presentation we're going to be doing stuff live so definitely take advantage of it um it's not going to just be a demo and something special to note typically we have our sessions our next experience platform academies every third Wednesday of the uh of the month but the third Wednesday of the month next month lands in the middle of knowledge and we are going to be very busy in a Vegas Expo floor where hopefully I get to see some of you guys so our next session is actually going to be June 21st the third Wednesday of June at 11 Eastern so be sure to tune in then and if you're going to go to knowledge say hi to us yeah we'll be all over the place we'll talk more about what sessions we're going to be doing at knowledge at the very and but this is now the second time I get to deliver this slide I'm very excited it feels like I'm officially an employee now this presentation may contain forward-looking statements because we are uh product managers so don't do anything based off of what we say don't make any purchasing decisions or anything like that based on anything you see here I think that's the gist of it yeah but the future things we we may say some things that are helpful but anything that we say is going to happen in the future could change so now let's talk a quick little intro into the next experience UI framework what even is this we're gonna start by talking some terminology real quick to make sure we're all on the same page here so the first term is the next experience UI framework which is the new JavaScript framework built on web component standards which works with the next experience UI which is the new user interface released in San Diego and this is the main difference you're going to see and there's a screenshot in the next slide is that the next experience UI has a purple default theme called Polaris and the core UI the previous UI 16 is all green so that's how you're going to be able to tell which one you're in uh configurable workspaces are our new way of working that replaces working out of the lists and forms and this called workspace UI and something to know oh we're going to hit on that one in a second Nexus agent Works place it's the Legacy workspace UI introduced in Madrid that has been replaced by configurable workspaces and a nice little quick way to tell those two aparts configurable versus Agent is that agent is kind of more blocky and green well configurable workspaces are a little bit more futuristic with curved edges like we said the core uis previously the UI 16 and the classic environment is what we are calling lists and forms which you used inside of core UI so as you can see on the left side you have the next experience UI in a workspace inside of the next experience UI and on the right side you have the core UI which is the green border around it and the forms and lists and things inside of it we call it the classic environment and there you can see one of the old agent workspaces you can see the main difference with the an example is the resolve button in both screenshots you see how it's purple and curvy on the left but Square on the right that's a that's a configurable workspace on the left versus an agent workspace on the right you can still use the forms and lists in the classic environment inside of the next experience they're just going to look a little bit more updated and modern there but that is what I wanted to go over before we continued on the next slide we're going to talk about our modern tech stack so this is the first pillar of our next experience UI framework it's a modern JavaScript framework built on open source web standards and our framework is similar to react it eliminates the need for third-party libraries such as angularjs or jelly and it allows us to create web components based on web standards which are future proof and adaptable we're not getting rid of angularjs at this time the service portal and the employee Center product still use this library and Brad will go over more detail about when it's appropriate to use each of them but this is the first part that I wanted to talk about of our next experience framework and then the next slide we're going to go over our component library in the servicenow CLI with the UI framework you can build components we have about over 200 out of the box components to use and if you're interested in keeping track of what's which components are coming out when I highly suggest you keep track of the release notes for them it's the best way to keep track of when things are released and when things are coming out we encourage you to start from our components and extend them to meet your needs but we also have the servicenow can command line interface for the CLI which enables you to create your own components and introduce them into experiences via UI Builder and now I'm going to turn it over to Brad and get to answering some questions in the chat all right this is me so we're going to talk we're going to talk about UI Builder and portals uh if you know you've probably seen this slide already if you've ever watched me give a presentation in the last year but we'll talk about UI Builder and portals then we're going to talk about workspaces and some best practices and then we'll actually get into an instance and poke around add some workspaces and kind of see some of the basic configuration and activities you can do in workspaces all right so UI Builder and service portal these are two different user experience technologies that we have a UI Builder is what we've been talking about uh so far that is built on our new next experience UI framework it's a web component framework similar to react but not exactly react and then service portal is our older tool for you know building out custom experiences it is built on angular and has been around for a while so let's go we'll go back to that slide so when to use UI Builder and service portal this is this is kind of the money slide when it comes to UI Builder and service portal UI Builder is really targeted at fulfiller type experiences currently service portal is really targeted at request or experiences so fulfill our experiences are generally workspaces or they may be kind of a small departmental type portal or just a custom UI for interacting with your application whereas service portal is really geared towards these Enterprise portals where you need responsive design you need to you know scan another portal and make it look exactly like that other portal you need a lot of catalog support you want to be able to use public pages and things like that so if you know if if you have kind of a middle ground experience that you're looking to build where it's not necessarily like a fulfiller based experience or not necessarily A requester based experience this is a good slide to take a look at and and you know think about like do I need responsive design does it need to be Pixel Perfect things like that all right so we have even more terminology so these are a few things we'll get into with the demo but the first one is this concept of app shells this is a fairly unique to servicenow This this term and so we use it pretty extensively so the app shell is really like an experience type there's two main app shells and that's workspace and portal and again the portal app shell is really for you know small departmental portals that don't need a lot of catalog and responsive design next we've got components which we talked about a little bit earlier these are kind of the building blocks of any experience so in the new framework components are similar to what widgets would be in a service portal in terms of kind of how they work but not how they're built or designed so these components are meant to be used they're meant to allow you to build out a whole experience generally you don't really need to do any customizations to the components they have lots of properties that allow you to control how they how they act UI Builder we've talked about this is our page creation and configuration tool allows you to you know create new pages and build out the experiences in those pages the Mac component is something I wanted to add in here the name of the table is assist under you underscore ux underscore macro opponent and the macro opponent is really a record that represents a page it's got a few different fields in it that have a lot of Json in it and so when you edit a page with UI Builder what it does is it saves your changes to the macro opponent record and then when the page is getting rendered it reads everything everything from the macroponent record and then kind of renders all of your components and events and and state parameters and all of those things so if you know you you see something kind of weird going on with a page or maybe you want to revert it to a previous version the macro opponent record is a good place to go check it may not you know make a lot of sense to you there's a lot of Json in there but that is the the record that generated with Pages we're going to talk more about variants but a variant is basically a different version of a page so you can have multiple variations of the same page so when you hit a URL the engine makes some decisions and then serves you up the appropriate variant of that page and then ux page properties we'll also look at a little bit in the demo but these are basically properties that persist through your entire experience so you can set a ux page property and then refer to it from different pages a lot of them are either sys IDs or some Json that that get looked at and there are a number of page properties that exist by default and you can kind of you know go into some of the experiences and take a look at it so I'll pause we'll go back to the slide there's a good question employee Center versus service portal so you're typing an answer to that question thank you I will not uh no go ahead let's make sure I want to make sure I'm right first I was just so employee Center is a service portal uh it's just our newest version of the portal that we're shipping by default uh and so that is our current recommendation if you need an enterprise portal uh you should go with employee Center and something to note is what does not support catalog items currently are the portal experiences built through UI Builder but the angular portal does support catalog items and that's what we're telling you to use in this in this slide right here third from the bottom yeah there's a new platform analytics workspace use the same components as the PA related components that can be configured in UI Builders yes the components are all the same we did do a pretty extensive next experience Academy in the fall on inline dashboards which are basically what you're configuring with the platform analytics workspace so I would go back and take a look at that because it has some pretty in-depth information all right and then if you want to see this page there is a there is a knowledge or not a knowledge article there's a community article with all of the information and this comparison on it on our Coe which I'm sure someone can can post in the chat oh I should have been on this slide when we talked about employee Center I forgot that this was the next slide so employee Center is uh is uh our this is a service portal so this is built on the angular Tech stack it's not the next experience UI framework but it is kind of the newest version of an enterprise portal if you are looking to stand up an Enterprise request portal all right so we're going to talk about configurable workspaces and UI Builder as of the Utah release so let's go ahead and take a look here so uh workspaces are built on this next experience UI framework that we have at the bottom both the new UI so the next experience UI and configurable workspaces are built on that framework and you can use a UI Builder to both edit next experience UI landing pages and do some configuration and customization to configurable workspaces on the right here we see that you can create your own configurable workspaces using App engine studio if you're licensed for that and uh yeah so sorry I I shouldn't look at the Q a while I'm talking uh it threw me off so you can build your own Uh custom configurable workspaces with app engine Studio we don't recommend you try to build your own without app engine Studio at this point uh because it's pretty difficult but we'll kind of get into you know why that is if you do build a workspace with app engine Studio you can use the workspace Builder which is a part of app engine Studio that lets you do a lot of the initial configuration of a workspace in a little bit easier way than just directly editing the workspace but again that only applies to workspaces that you build with app engine Studio you wouldn't be able to use workspace Builder on any of the configurable workspaces that we are shipping by default I also see that we have a question is it possible to configure your agent calendar and workspace I don't know what agent calendar is so I don't know the answer to that question but we can try to try to get you one when we when we get this posted all right so where do you get started with workspaces so we strongly recommend that you start from one of the workspaces that we Ship by default I think I throw out different numbers but it's between 20 and 25 uh configurable workspaces that we're shipping by default uh in uh in Utah uh and so there are generally workspaces for most of our different process areas um so itsm itom HR CSM FSM all of these uh all of these acronyms that we have have their own workspaces and we recommend that you start with that workspace that you don't try to clone a workspace that you don't try to you know build your own from scratch if you have um you know if you're wanting people to interact with incidents for example they should be using service operations workspace if you want to use a workspace so most of our product lines have a workspace they're built to be configurable that's why we call them configurable workspaces it's it's built to have you configure it implement it customize it so you should not be afraid to do that and we're going to get into okay you tell us that but how how do we customize those workspaces the second one is if you have an application that we don't have a workspace for which generally is probably a custom application that you've built maybe with app engine Studio you can use app engine Studio to generate a workspace for your application and again you'll you'd be able to use the workspace Builder and it's uh it's a fairly easy way to stand up a new workspace it is technically possible to create a workspace workspace from scratch if you if you've tried it you know that it can be pretty difficult so it's not something we recommend unless you absolutely have to create a workspace from scratch uh like if you're not licensed for app engine Studio but have some sort of custom process with a user base that doesn't already have a workspace to use you can do that it is fairly difficult and really the best way to do that is to take a look at all of the ux page properties that are associated with some of our out of the box workspace and then try to replicate those in creating from scratch but again we don't really recommend that you do that I've mentioned some of these workspaces we also have an article out on the community that lists most of the workspaces that we ship out of the box and it has links to all of their documentation so check that out I don't know if that's in the q a but we can post that link as well so yeah so what we have on the slide these are some some of our most common workspaces here uh service operations is our most used workspace CSM HR agent workspace uh and then some of these other ones um are are there as well and this is just uh this is maybe less than half of the workspaces that we actually uh ship so there are a lot out there so let's take a look real quick at some workspace best practices or good practices because some people don't like uh to use the word best practices but the first one is that each workspace has its own documentation and so we'll we'll look at this we're going to do in the demo we're going to compare like CSM I think CSM to service operations workspace and kind of show how they're different but I you know UI Builder workspaces components the framework this is all just some some platform tooling that are platform engineering teams have built that then all of our application teams take and build out their own products with right so what that means is that you know one team may build something differently than another team and you know this is this is not unique to workspaces you know in the past you might have seen that you know maybe one of our maybe itsm builds out some flows that work a little differently than the ways CSM builds out flows you know it's just kind of the nature of when you give people lots of tools they may build things a little bit differently so that it's very important to look at the workspace specific documentation because the way that you can figure something in one workspace may be different than the way that you do it in another workspace and so examples of that are maybe the the landing page of a workspace like service operations workspace has a pretty unique way that they built their landing page and then record page tabs depending on if the workspace is using the standard record page or not the same thing with lists sometimes lists can be configured a little differently but uh but you know for the most part lists are pretty consistent across the workspaces so let me pause we have some awesome questions for you Brad are you ready yeah I'm ready can we expect responsiveness to be added to uib Pages as well I wouldn't expect workspaces to be responsive um but I that is a it is a thing that we are looking at um so we know that at some point uh if we offer you know Enterprise service portals uh on this new framework those have to be responsive um so you can't have a portal that's not responsive in 2023 so it is a thing that we are looking at I can't I you know I can't give you any sort of road map date for when we would deliver that awesome and just to confirm Mark asks did I see you say out of the box configurable workspaces are not editable through app engine studio so it kind of depends so so uh workspace Builder is a tool embedded in app engine studio and it only applies to experiences that workspaces that you create from App engine studio so you wouldn't be able to use workspace Builder to work with service operations workspace right now it's it is very specific to any workspace that gets created from App engine studio so app and engine studio is a tool geared for making it really easy to build out custom applications so something like service operations workspace is not a custom application it's a thing that we Ship by default and so you wouldn't use app engine Studio to work with you know itsm or service operations workspace and the next one is do all servicenowship workspaces in all products have their own scope and what is the technical reason for having the workspace in a scope that is separate of the product that it belongs to yeah that's a good question I would say for the most part the workspaces have their own Scopes and some workspaces span multiple Scopes and there's a few reasons for that so one of them is it makes it easy so so one of them is a lot we've tried to deliver a lot of these workspaces through the store and anything we deliver through the store has to be scoped and if we deliver a workspace through the school through the store you may want to enable CS SM but not have the workspace so that's why the workspace might be in a separate scope but yeah so generally putting something in a separate scope is really about being able to deliver it separately update it separately and then also you know some of our like service operations workspace has an itsm scope and an itom scope because it can span both products but you may not be using itom you may only be using itsm so you wouldn't want the itom things in your workspace in that case so it's really about being able to deliver separate parts of workspaces or workspaces separately on top of the products is there a way to transfer all of our configurations AKA like uh UI policies Fields visible Etc from our classic agent workspace so the new service operations workspace or are you going to are we having to build it all from scratch again so like a UI policy is not workspace specific so it should work you know if your show going and hiding a field based on another field that should work the same way in configurable workspace as the form but I guess to answer the question more broadly there will be some things that if you configured an agent workspace it'll also work in configurable workspace that was kind of the goal and there will be some things that you might have to reconfigure in configurable workspace but we should pick up things like you know UI policies and form views and things like that should automatically get picked up with configurable workspaces if that makes sense thank you and we're getting some more in-depth questions a great place to go for answering for getting answers to more in-depth questions that are a bit more technical that we can't go over in a live stream like this is the snws.com server we have a our own channel on there where we are answering questions at all times so feel free to drop by and ask us the more in-depth questions there as well yeah and and I there's another question I saw on the QA q a around basically around how do I you know how do I move workspace customizations and so workspaces are trash effect and move just like anything else you do in a development environment you can use update sets or you could use the app repo you can use Source control and so you know all of those things work generally so something I put on here in this second bullet in the second Dash here work in the workspaces scope so generally that's what our engineering teams advise is for if you are going to uh you know create a variant of an existing page so you can customize it you want to do that in the same scope as the as the existing page because it's possible that the the original page could have some client scripts on it which are housed in separate records and they could have some cross scope access issues so generally it's safest if you work in the workspaces scope that could involve you having the four different Scopes you're working in for one workspace if it's service operations workspace and so in that case you'd want to make make use of update set batching and things like that but going in the second bullet workspaces were meant to be extended and configured and so the best way to do that is to duplicate variants of the pages and I'll show what that looks like in a little bit when we get into the demo but uh but you know we most of the pages that we Ship by default are read only so you can't you can't update them but you can duplicate them and then order your new variant to take precedence over the existing one and so that existing page you know if we made an update to it that page would get the updates and so you'd want to check and see if you want that update so you know because because we have we've got a platform and then we have all these application teams that are building on the platform uh we may you know really lease a new platform feature and it may take a release or two for our application teams to integrate that new feature into their workspace so an example of that is the standard record page so in the Tokyo release we came out with this concept of presets and controllers where if I have a preset enabled component and I add it to a page it will automatically pull in a data resource called a controller and map all of the properties that it needs to use and so it makes it really easy to build out record pages in forms and makes the record page easier to work with but the HR agent the HR workspace is using the standard record page but service operations in CSM are not using the standard record page yet so that is you know eventually everyone will uptake it into their workspace but different application teams kind of have to work it into their roadmaps when and they'll uptake this the other one is user presence so you know workspaces can be enabled to use user presence and that's another thing that the application teams kind of have to pull into their workspaces as they're doing their development and Road mapping all right awesome great questions everybody so we talked about this a little bit already I won't spend much time on it but agent workspace we would consider agent workspace Legacy right now if you are not on workspace yet and want to move to workspace we recommend you do not move to an agent workspace you move to the appropriate configurable workspace for your product so agent workspace was kind of our first shot at workspaces uh it is very rigid is the main problem with it you can't really do much configuration of the pages outside of the landing page and so configurable workspaces are really where we're investing all of you know our time time and and development uh in terms of making those better all right then we've got a few slides around uh analytics and then we will jump into a demo and do some more q a so analytics Center or platform analytics workspace is something I wanted to talk about here but this is kind of a new experience for creating reports and dashboards that you can uh you know allow your users to use so they could create their own dashboards in this workspace so we'll get there on the next slide but uh it is kind of a newer way uh to uh to allow your users to do reporting and analytics so one of the things that this new workspace has is the inline dashboard editor we did a whole Academy on this but the inline dashboard editor lets you create dashboards where you can add all of these data visualizations and filters to a dashboard and uh it all kind of automatically works together and then you can also if your dashboard is just a little too complex and you have the uh roles in the instance to use UI Builder you can go from the inline dashboard dashboard editor and convert it into a UI Builder page and work with it in the UI Builder if you need to add even more functionality to it and then visualization designer lets you create data visualizations that people can then pull into their dashboard so if you had some really Advanced Data visualizations you wanted to create that you wanted to then make available they could do that it's pretty similar to you know reporting and responsive dashboards where you can pull your reports into your dashboards but this is the newer dashboard technology and this is really where we're headed with all of our reporting and dashboarding so the first version of this was Tokyo we have tons of updates planned for Vancouver and Washington so you'll see you'll see this this dashboard and inline dashboard editor functionality really grow over the next few releases with that I think we'll go demo now and then we'll jump back into the PowerPoint while it's loading we'll we'll uh answer some more questions is there a way to convert our current dashboards to the new dashboard tool or is that not advised that is not a thing I would worry about yet I don't want to get too specific but that is a thing that will be addressed in a future release I believe performance issues oh you go for it will there be any performance issues so so I would say there could be so in terms of uh well I didn't need I didn't read the whole question so that doesn't make sense so the question is will there be performance issues uh in the instance due to too many dashboards or reports running so that that is one of the biggest causes of performance issues in any instance are basically home pages and reports that's actually one of the reasons that we we didn't introduce like Auto refresh into the newer dashboards because it's really easy to abuse that auto refresh functionality if you've got you know 100 people that have added tons of reports to a dashboard and then set it to refresh every five minutes that can affect your instance performance but in terms of like will you see a different performance hit I don't I don't think you'd see anything different just because you know you'd be moving from using uh you know Dash responsive dashboards and reports and the classic environment to doing it in a workspace you know people are still you know seeing dashboards and reports so I don't think that would be any different the other question so service operation workspace there's a question is it focused on tier one or tier two I believe it is the the workspace to use for itsm it is I believe it's tier one first right now but uh yeah I'm not a I'm I'm a uh I'm more of a UI Builder workspace expert rather than the specific workspaces and obviously since there's more than 20 uh it's hard for me to keep track of what each one does and all of those things so uh let's go ahead and uh and poke around a little bit um so this is a Utah instance uh you can see that I've got the little workspace menu I have a few different applications installed on this instance like HR agent workspace service operations workspace I did not put CSM on this one so we won't compare those but you've got cmdbs at those so let's uh let's jump into one of them so service operations workspace is our most popular workspace which makes sense because it's the itsm workspace so that's loading uh one of the things that we're working on over the next couple of releases is initial page load time so we know that that's an area where uh we have the opportunity to improve and so the initial page load time for a lot of these pages is can be a little longer than we'd like it to be we do a ton of caching uh with uh with the workspaces so after you initially load one of these it should load faster uh later on but that initial page load is something we're working on so this is this is the workspace uh you know we've got uh lists here and I'll kind of show how those get configured but you've got the the list in here and you can click into those and see records if I don't I don't know that I have any records in this instance but let's take a look at we're just going to look at a few of the main things that you need to know when you're working with the workspaces so I'm going to open UI Builder here while it loads um Ralph has a question the needs of service desks are different from tier two teams this is our new workspace focus on Services rather than tier two as they view service operations workspaces focused on tier two yeah I would say service operations workspace is I think it's tier one but we you'd probably need an expert from these service operations team uh we can get a better answer to that but I I think they started with tier one and then our branching into tier two but again we are we are on the platform side of things and not necessarily an expert in each product area I don't know what do we want to start with let's start with service operations workspace all right so I'm going to open uh service operations workspace and UI Builder it's going to give me the experience view which is new in Utah uh this is one of my favorite things in Utah is the experience view so instead of just adding me into the default Landing landing page which I changed the URL path on it for some reason when I was doing some testing it shows me this map of my entire experience so one of my favorite things is that I can see all of the uh all the all of the page variants so something like the record page that generally has a good amount of variants I can see all of them I can see what what their orders are and then I can jump in and edit a specific variant of a page which can be really helpful so what we're going to do is we're going to jump into this default landing page that I have called The Snug page and if this is right there's a question about audiences and I'm I'm going to get there so I've I have messed with this one let's let's do a different let's start with the HR workspace because I know I have a mess with that this is a highly planned demo obviously um so this is the the HR workspace and so I want to open up the list page and so you know we showed that uh you know I can go to the little list icon and see my list that looks a lot like the you know the all menu or the left nav uh it looks like this and so one of the most common questions one of the things you want to start with is what how do I you know how do I edit this stuff and so one of the there's a couple of different ways that you can get to this but the easiest to me is just opening up this list page uh clicking on the list nav component so this is all one component on the right here you can see in the config panel these are all the components properties so this is how you tell the component uh how it needs to behave and what data it needs and then one of the things that we have is this configuration link so if I click on that link it's going to kick me back out into the classic environment and it's going to show me all of the ux list menu configurations and so I'm going to take uh no we were in HR which is this one uh and so that's gonna give me my categories and then all of my lists so it's from here uh where I can come in and you know I can add lists and categories similar to how you would add application menus and modules in the all menu I can reorder things I can you know change the filters all of that sort of thing but I can do that through uh this configuration uh there so that's uh item number one uh how do I how do I edit what shows up on the list page uh we do that through the list through the list page and through the list nav component so one of the other things that I want to look at uh let's say I wanted to make some changes to the landing page so this is probably the most common uh page that people want to change they'll come in and want to change the landing page and so I'm going to change to a different scope uh most of our most of the pages that we ship are read only by default um but uh it looks like the HR page you can uh you can edit if you wanted to uh we're not going to do that what we're going to do is we're going to leave this page as is and I want my landing page to look a little different so I'm going to click on little hamburger icon and I'm going to sit I'm going to say duplicate variant and then uh let's call this uh Brad's landing page and then we had an audiences question so audiences are basically by default it's role based and so I can say you know these three roles mean that this is the the user is an HR user and so I'm sure I have an HR so we've got an HR case writer audience so sure let's set that and then I can open all of the audiences on the classic environment if I want I can also set conditions and so for conditions you're looking at a page parameters So based on what I'm passing a page through its URL I could show different variants based on that or I could use audience or I could do some sort of combination of both of them so let's go ahead and create this so there's a question yeah yeah perfect go for it there's a question in the chat about uh service operations workspace and landing pages yes so the answer the answer is basically you can configure landing pages uh for when somebody first logs into the instance if you have the next experience UI turned on um so that's actually the unified navigation experience you can go in and create variants of that landing page and so the way that service operations workspace does it is they have a variant of the unified nav landing page and it just redirects you to service operations workspace and so that is one way to do that so this is my new landing page if I click in I can see that we have that default landing page and then we have mine I could change the order on this so if I go into settings I could say hey I want mine to show up first and I could make the order negative 10 and save it and then if I look here we have switched the order of the landing pages here so now anytime somebody hits this page if they have the Right audience they'll get taken to this page instead of the other landing page so this would be where you know I could come in and you know remove some components I could add components I could move things around but creating variants is is really the way to do that so you can configure a list through that list configuration tool if you want to come in and customize a page you want to create a variant of that page and then you own this new page this new page variant and you can customize that so let me look through the Q a a little bit how do audiences come into play for different views for different workspaces again audiences just apply to variants so you're looking at which variant you're showing if we're talking about form views that would be I think using a view rules if I remember correctly but different than audiences we had a question can we show configuration of custom buttons in the action we do have some enablement on how to do that it's a little bit longer activity than the eight minutes we have left so I won't show that here there we are working on making more of these images uh either removable or changeable and that is something that is coming in the future so look out for that and then we have a question about views and workspaces so that's the last thing we'll touch on before we hop back into the PowerPoint but let's go ahead and look at the record page here let's look here that's fine so let's open up a record page so the record Pages uh we're not going to see anything because I don't have the parameter test value set up but basically there's a form component and the form component has a view review property and so this is what is telling this page which form view to show in the details tab so this View Property this is coming from a record data resource and it's reading that view from the ux page properties for the experience so if I were to come in and look at uh the HR agent workspace experience I should have a view let's go is it HR human resources I guess I could have just clicked on it so these ux page properties um are basically just properties that you set on an experience specific basis and I believe it should have a view yeah so it's got a view property and it's set to the workspace uib view I believe and then there's some view rules there's a view rule configuration and a lot of these things that we have documented on the Coe and so it'll tell you kind of how to work with some of these view rules uh in views um but basically yeah the uh the form component has that view property and most of our out-of-the-box workspaces it is controlled through the controller and the controller is reading it from the ux page properties let's talk about what we're going to be doing in knowledge and Creator con we have a bunch of awesome stuff lined up for y'all we are going to be doing lab sessions as well as regular Creator con breakouts and knowledge sessions so we're gonna have uh Brad leading another building a killer blank experience I love doing those labs uh we have a theme Builder lab as well as a theme Builder ask the expert session same with next experience access per sessions we also have a roadmap session for the future of next experience so you guys should take a look at the agenda Builder it is now up live on the knowledge website you can go in there and start signing up for stuff if the sessions that you were wanting to get into are full you should try again maybe in a couple of days if not a couple weeks they tend to open up new sessions as the really popular sessions get full our theme Builder one right now last I checked was full it's super popular so if you want to have some theme Builder fun and knowledge you should definitely show up awesome so next let's talk about some resources I have linked in the chat the next experience Coe it is the absolutely bestest place to have all of the most completest information on next experience theme Builder UI Builder and all of that and if anything's missing just let us know and I'll make sure to add it um we also have next experience and UI Builder courses on now learning there's the next experience YouTube playlist and then there's the next experience Community if you have any questions to ask next uh make sure to join us for all of our future webinars and meetups uh you can scan the QR code and see the live on servicenow events there you're able to sign up for things like more Academy sessions such as these wonderful Academy sessions like I said the next time that we are going to be meeting is going to be June 21st at 11 A.M Eastern just like today because next month it's going to be knowledge time I hope to see y'all there if you see me I'm gonna be wearing fun outfits y'all should come say hi to me and Brad as well of course and Ashley and y'all are gonna get to meet Samantha as well so be sure to sign up for our Academy session stay tuned and then one last thing before we go so we did have a question I wanted to address before we drop somebody asked for Labs at knowledge if you haven't been there you do need to bring a laptop a laptop is easiest if it's if it was me I would bring a laptop and a tablet so I'd have the instructions for the lab on my tablet or phone and then work the lab on my laptop but you should bring something to do labs to knowledge awesome and then thank you so that is the last of it the next thing the very last thing I wanted to say before we dropped off is that tomorrow we are having a uni Builder live session this is a weekly to bi-weekly question mark uh we've been kind of busy recently so we've not had it in the Cadence that we kind of expected but it's a live stream it's a lot more relaxed and laid back than an academy would be it's another great place for you to get live one-on-one interactions with experts like Brad and learn more about workspaces next experience uh the UI Builder and all of that it's going to be sort of a continuation from today's session so if you have more questions after you go home today and play around with some workspaces be sure to show up tomorrow it's going to be at 4 pm eastern time I'm going to drop a link in the chat it's on the servicenow Dev program YouTube channel so be sure to come and hang out with us tomorrow it's going to be a lot more laid back think of it like a non-alcoholic life coding happy hour and that is it for me how about you Brad that's all I've got uh thanks everybody this was a fun one and yeah if you have more uh you know if you want to see more workspace stuff we're going to kind of do an extension of this tomorrow at the uni Builder on the dev program YouTube channel thank you all so much have a good day happy Wednesday thanks everybody