[Music] hello everyone um thank you for joining we're just gonna give it a little bit of like a minute or so just to allow some more participants to join in all right awesome so we'll go ahead and get started um thank you again for joining our next experience academy um this is so exciting this is our first um kind of split off of our own academy um you may have seen us on previous academies for like the platform foundations academy where we did have some sessions but this is the first academy fully dedicated to all topics next experience and we're going to have these academies they're going to be monthly right now um so we'll have one every month and send out reminders we'll have them through the end of 2022 and if we keep getting more topics maybe we'll up the cadence from there but just so you're aware monthly um every month on on wednesday around 12 p.m eastern standard time just keep a look out for the invitations and the community post on our forum um i do want to mention just some housekeeping before we get started with the introductions if you do have questions please put them in the q a instead of the chat and we'll just get to them throughout the session um so i'm going to introduce myself and then we'll get to the other members of the team my name is ashley snyder i'm an outbound product manager for the next experience team my focus areas are on next experience ui inconfigurable workspaces i've been with servicenow for about eight months and just really enjoying being on the team working with next experience i'll go ahead and hand it off to you brad hey everybody my name is brad tilton and i am also on the avalon product management team for next experience uh my kind of specialty area i guess is ui builder and builder experience uh but yeah we uh we cover all of next experience i'll just throw it to amanda hi everyone thank you all so much for joining our first next experience academy my name is amanda joslin i'm the director of outbound product management here at servicenow i've been here a little almost three years so really excited for this to bring you all this content and we're looking forward to a really engaging session so feel free to ask questions in the q a um raise your hand if you want to ask a question live um but we're looking forward to to hearing from all of you as well all right thank you guys we'll go ahead and get started letting me get um our session queued up so brad and i are going to be mainly leading this as far as slides um so we'll kind of be switching off here and let me make sure you guys can see my screen so this session is our kickoff session um it is kind of an overview session of next experience for those who may be new to it as well as a roadmap because we have done some previous platform academy sessions on what next experience is we do have an activation one as well so do encourage you to kind of go back and look for those previous um sessions that we've done um just a safe harbor notice so um you know a lot of this material since it is a roadmap session is going to be um forward-looking we do uh encourage you not to make any purchasing decisions based upon the material provided in this session i'm still going to mention it's going to be an overview session we're going to start with what next experience is um we're going to just touch base on some quick activation information uh we're going to take a look at what we have currently as the san diego release and then introduce some new features for upcoming the upcoming tokyo and utah releases we're going to wrap up the session on some great resources that we have for you as far as getting information on next experience and then we'll have a just a short demo and some time for q a like we mentioned please ask questions throughout the sessions we'll try to answer those but we will have time allotted for q a at the end as well um before we get started we're just going to have a quick poll we're really gauging where everyone's at with this um so we'll just give a few moments for the poll all right everybody should have the zoom pole up and here we go we're getting some answers looks like we are kind of neck and neck between i've heard of next experience and or ui builder but not used it and i've heard of next experience and or ui builder and have used it so we're about half and half there and only a couple of people had never heard of white builder okay that's good to hear that only a small amount of you haven't heard about it yet um hopefully this is a great introduction for you guys all right well in the poll here all right and just before you move on there is a question about licensing so um i just want to address that off the bat because it's a good thing to start off with um we are product managers so we are part of the team that develops the product we are not familiar with licensing or how it's licensed or which is in which licenses those change quite frequently so it's best to talk to your account team about that um definitely take down notes um and we can follow up ui builder is part of the platform so you do get that as part of the basic platform however there could be changes on you know some of the uh the advanced features we talk about today so definitely follow up with your account team it's the best course of action but thank you john for that question i think it was good for everyone to hear that off the bat thank you cool so we'll go ahead and get started with our next experience um overview um and uh if you haven't had a chance to really review any next experience information um we do have product documentation up we're going to dive into some supported use cases for next experience and some information on the san diego release of next experience so i did want to kind of start out with some terminology on what next experience is it is kind of a bunch of things uh all in one we do have our next experience ui that we released in san diego which may be the first thing that kind of comes to mind when we talk about next experience but it is actually kind of an umbrella of different terms um so first off it is our tech stack that is built on top of our ui framework it was previously called the now experience ui framework if you see that in some documentation or literature if you hear next experience ui framework or just ui framework it is the same thing it is our javascript framework that is built on top of open source web standards which really eliminates our dependencies on third-party frameworks such as angularjs or jelly and does future proof our user interfaces and products going forward and we've used this framework to create over 150 out of the box components and we're continuing to build more um and the ui framework can also you know be used with our servicenow command line interface for you guys as customers to create your own components as well we've hooked in the now design system to provide a modern look and feel that can be applied to experiences all the way down to the component level and our product experiences can be configured in ui builder so customers can use the workspaces that we're releasing or they can create and configure their own application experiences as well as using a drag and drop user interface and configuring different component attributes and events all within ui builder so you use ui builder not only to configure the workspaces we release or the experiences that we release but also if you're creating your own if you're creating them from app engine studio you'll use ui builder to configure those um as well um so while we're focusing on creating workspace experiences right now in san diego we don't plan on stopping there um it's not not the only thing we plan on doing with ui framework and next experience but that is our current point san diego and most of our products do have their own configurable workspace as of the san diego release and then finally we've used this whole text stack that i just mentioned to create the next experience ui is available in san diego um and it is built off the same ui framework that is used for the rest of our experiences and then the ones that you create too so why next experience ui um so responding to customer feedback that our platform is very extensible you can do a lot with it but really just look outdated we begin to invest heavily the last few releases to develop a robust modern and consumer-grade user interface that has a customizable look and feel we've moved the application navigator sidebar to a new extensible top menu system to free up screen real estate but you do have the option to pin menus as well if you're used to working with that sidebar experience you can easily see where you're at and create new favorites using the contextual app pill and the unified navigation header allows users to navigate back and forth between the classic environment or you know what we previously called forms and lists and workspace experiences within one browser tab in addition to elevating the look and feel we have introduced a dark mode for increased accessibility and have updated the styling on our classic environment list and form so prior to san diego our focus on workspaces was mainly around tier 1 and tier 2 fulfillers or agents mainly working in areas such as csm or itsm our footballer and agent-based workspaces do provide agents and case managers service desk professionals with the tools that they need to answer customer questions and resolve customer problems they can see from a single view like the full context of the case or the incident or record that they're working on we've embedded ai assisted recommendations things like playbook experience advanced work assignment and agent assist all within these workspaces to really give the agents tools they need to resolve issues fast but we have expanded workspaces past billers and agents as with san diego we offer workspaces for areas such as cloud operations hardware asset management grc based processes such as risk compliance and audit management we have workspaces for strategic portfolio management such as the alignment planner workspace project workspace procurement specialist workspace and as well as a brand new hr configurable workspace so definitely encourage you to check out a workspace for a product that you're using more than likely as of the san diego release and one exists for it um brian i'm going to go ahead and hand this off to you real quick as far as questions on ui builder and service portal and the differences thanks ashley uh this is a big topic we generally get lots of questions around you know ui builder service portal portals what do i use when so right now ui builder is really geared toward fulfiller experiences and service portal is our tool for requester experiences so uh you know ui builder you can build workspaces that's really where we're you know we're focused uh in terms of fulfillers um it's a good way to customize workspaces or generate your own workspaces using app engine studio and then service portal is still our recommended tool for building requester experiences uh you know the technologies are different um eventually this will change but this is kind of the lay of the land for the foreseeable future so if you're making a decision right now on should i use ui builder should i use service portal uh it's really that persona based fulfiller is ui builder request or service portal uh and then you know there are some experiences in between that uh that you know may not be like a tier one or tier two agent working on tasks and it also may not be an end user with no training requesting something from the portal and in those cases if we can go to the next slide we've got a little bit more of a breakdown here so again target audience on this one workspaces versus enterprise portals and then you know starting in this fourth row here is really where you can kind of use this chart to make some decisions ui builder is not responsive by default like service portal is so if i look at a ui builder experience on my iphone or android phone it's not going to automatically look nice like service portal does um it also doesn't currently support pixel perfect design uh so in service portal you basically have complete control over the widgets and you can just drop style sheets in ui builder the experiences are built a little differently to where it does let you reuse components a lot easier than widgets but the other side of that is you can't just make it look however you want um so pixel perfect design if that's what you need you know that's still a service portal thing we have really limited support for catalog like anything outside of just using a record producer to create a record i would recommend using service service portal and then currently we don't have support for atf and ui builder and doing public pages which are basically pages for unauthenticated users is currently doable but it's pretty difficult in ui builder where as for service portal it's kind of natively able to handle that uh so because of you know because of these differences that's that's one of the reasons that you know the personas are really important because requesters generally need things to be responsive you know publicly supported things like that and that's why service portal is still our answer uh for requester experiences well thank you brad um yeah definitely go ahead and screenshot these um we'll have an article up on our coe with this information as well i think this is going to be really great information to have on hand and something that a lot of our customers have just been asking for kind of that decision tree on when to use both so definitely really appreciate the information cool so next we'll just get into some information um on how to activate next experience uh we do have a platform academy session i believe it was in april where we really went into depth on how to activate next experience some considerations that you might have and that um session is on our forum it is on our coe so you do want more in-depth information check out that session i'm just going to cover some basic steps to consider when activating the next experience um so first off before you activate next experience in sub production just read through the product documentation see if they're supported and unsupported features if you're a customer that is upgrading you may need to remediate some client-side scripts depending upon your level of customization we do have some guidance there on the product documentation we don't have any hard recommendations for remediation um it really is dependent upon you know your instance and the customizations that have been done we can offer some guidance and taking a look at any kind of ui scripts that modify elements such as the ui 16 header or application navigator this is a great place to start more than likely these modifications will not work with next experience but also check for any other scripts that may have things such as dom manipulation those would be great places to start as well i do want to mention any modifications made to the service portal are not impacted the next experience ui does not modify the service portal so if you do have those concerns both of these technologies are decoupled definitely test your service portal um in your upgrade testing the next experience does not make any modifications to that also make sure that you pat in some training time for your admins and your users in any knowledge or training materials that need to be updated to reflect the new user interface after that you're pretty much ready to activate the next experience ui this is as easy as setting a system property to true um if you're a new or z boot customer you'll already have next experience activated by default um and we're making it easier to activate next experience in tokyo we're just going to have like a one click tool that pops up um once you upgrade to san diego or to tokyo um and then we are working on a readiness checker tool that will check your instance for things such as if you're using connectchat guided tours and we'll have some other checks as well and we'll be providing kind of some guidance and support materials in that readiness tool and that will be an upcoming store release so we've laid a really great foundation to for our customers to start using our workspaces create their own next their own experiences and start using next experience ui um what's next we're going to start talking about our roadmap here and we're going to start with some enhancements that we've made to the unified navigation in tokyo so the first one is really exciting we are releasing what's called sidebar in tokyo and this feature allows for agent-to-agent conversations to occur on records so agents can collaborate on a record it does replace kind of that direct connect chat feature on a record itself due to connect chat not being supported index experience users will be able to view user presence within conversations so you can see who's on that record you can see who's chatting on that record you can perform drag and drop file sharing receive notifications and if you have some other features here that are noted on the slide so within unified navigation you'll see a badge counter displaying any kind of incoming or unread messages you can pin or unpin the discussion panel as you need and you can have multiple discussions at once on a record if you need it again i do want to mention this is for record-based conversations at the moment so it won't apply to other areas such as visual task boards or other areas that connect chat extends to but this may meet your requirements for replacing connectchat if you just want that record to record based communication so definitely check this out in the tokyo release i do believe it will be a store application as well and get familiar with it to see if it replaces that functionality that you need the next feature i want to mention is um for administrator configurable menus this is also another really exciting feature so this allows for administrators to now create and configure their own menus up in the unified navigation header so as of san diego we have four out of the box menus um you know all favorites history and workspaces and now admins can create menus for users by role so users may need to navigate to certain applications or modules and now they don't have to use the all menu or create favorites to do this you can create this menu for a certain role and this user will get it as soon as they log in and administrators can choose to only show this to certain roles or exclude certain roles and it does this feature does support domain separation as well all right brad i'm going to hand it back over to you for some ui builder enhancements all right yeah so ui builder there are a few uh enhancements uh in tokyo uh this is one of the big ones that's mostly under you know under the covers uh you know you're not gonna see a ton of uh results from this in tokyo but it's gonna set things up longer term but we came out with a new or we kind of re-architected some of our component technology to use presets and controllers is what we're calling them and it lets components basically auto configure themselves when you add them to the page and so we saw that you know it was taking a long time to build out your own record page if you wanted to build out a record page that's slightly different than our template uh it was signific it was a significant amount of time to build this something out that you do the same way every time so what we what we did with this record page template was we built it out on these presets and controllers and now when you add one of our form components to a page it basically auto-configures itself a little bit and it uses controllers to fetch data so it'll automatically add basically a data resource for you and then map uh the results from the data resource to the right inputs on the component and so that was something that used to take a while and you had to kind of figure out where in the you know where in the data return from your data resource you have to map to the right place on the components uh so the form components are what we started with on the record page uh and eventually we're going to uplift a lot of our components with this newer technology so that's probably the biggest thing in tokyo although you know you you may not see a lot of results from it right away outside of the record page template i do believe we have some other enhancements too but i think brad we're going to have an upcoming session on ui builders so we'll have to wait until then um for the upcoming roadmap on that um so i'll go ahead and move on to a feature um that is slated for an upcoming release it's branding manager so if you're on san diego if you've used sex experience ui you may have played around with theming or explored theming a little bit uh we did release a powerful new theming engine with next experience where you as customers can theme the next experience ui um you can theme experiences and you can theme all the way down to like the component level um using ui folder right now as of the san diego release customers do have to input css variables in a json format manually through it for a theme we do have some some center of excellence documentation and i'll get to the center of excellence in just a moment that does assist with this we have documentation on how to create your first theme how to apply a theme to different instances so if you're used to doing you know a theme for production versus subproduction to really follow that best practice on where you're at we have information on that um and even some articles on like how to convert ui 16 themes over i do want to mention one thing that if you do have next experience enabled that the theme will also apply to any configurable workspaces that you may have because they are wrapped within that unified navigation header there's not a way to theme individual workspaces at the moment with next experience enable but this is something that we're looking into on our roadmap um so we are releasing a branding manager in an upcoming release it is going to be a gui interface that allows you to manage edit and implement themes in an easy efficient and upgrade safe way just to make it really easy to reflect your company's branding branding manager is going to walk you through generating a theme with just a few branding colors it will display a theme preview so you can actually take a look at the theme before applying it to any instance and see if it's what you'd like once you've created a theme you can go in and use branding manager to go and fine-tune the theme down to different css variables if you need so let's say you want to change a certain thing here or a certain thing there you can do that all within branding manager um so be on the lookout for that in an upcoming release and then we'll have more information about it um it is really exciting uh as far as being able to not only the next experience ui but we're hoping to really make this a tool for a lot of gaming needs across the instance as well and we'll go ahead and wrap up just a few more product enhancements that we have um so we are continuing to invest in what we've currently built for next experience so a few enhancements to note for tokyo we've made some performance enhancements to configurable workspace lists that have really large data sets so that loading time is reduced and list timeouts do not occur so if you are a customer that has a large data set like a million plus records you may have seen timeouts in the past or slow loading times we've prevented this with the tokyo release so definitely go back and revisit that there if you've had those issues we've had productivity enhancements in workspaces such as user presence which is a big one so i know we had that in ui 16 in the classic environment but now we do have it in our workspace forms as well so you can see who else is on the record and different right-click actions such as jumping to different form sections personalizing the form refreshing it and all the actions such as copying urls and cis ids that you're used to we've also added attachment sorting sorting as well so you can sort attachments from newest to oldest or vice versa on that form and then just a few things to the email client we have in compact mode in full mode in the email client composer as well as adding a few more configurations to the email sidebar um these are just a few to know we do have more enhancements coming out and we will have that information on our center of excellence once tokyo ga is available cool so like i mentioned a lot of our content is on the community um our center of excellence site is a great place to look for migration guidance best practices new release information training resources and more i have qr code for it right here and i also we have a short link right above the header up here if you want to go to it and um this center of excellence site is located on our next experience forum on the community which is another great resource for you to subscribe to or bookmark um it's the same as our of other community forums where you can ask questions and get answers to your next experience questions cool so i'm just going to drop into a quick demo um and then we'll we'll get back to another poll and q a so i did want to show off um the admin configured menus that we have in tokyo you may notice i'm logged in as the admin right here and by default i already have a new menu called admin where i have a link to this landing page here and something called it adoption journeys i'm not going to go too deep into what this is for this demo there is a new product called admin center that we have product documentation on so i do encourage you to check out that documentation on what admin center is and what it can do for you but i'm going to show you guys how to create your own uh admin configured menus so if you go over to the application navigator and just type in unified um underneath this now experience framework menu you'll see something called unified navigation configuration and this is where you can go in and modify those menus i cannot modify the out of the box menus we do have acls on those you can come in here and create your own or add the ones that you create so um for this example i'm just going to do like a product owner who may need some agile modules just to show you how you can control this by roll so i'm just going to give this a name i'll give it an order of 6. i'll go ahead and activate it and i'm going to give it scrum user role and also i'm an admin i do not want to see everyone's menus so i'm going to go ahead and hide it from myself so my unified navigation doesn't get cluttered um one thing to note you probably will not see this until there are some um unified navigation menu items added so we do have to have some applications or modules present for this to work um you can right now switch between an application or a module i'm just going to set up some basic modules for us so let's do we'll do the agile board and i'll just set that order of one and i'll do two more we're just going to do epics and stories oh oh i'm underneath application all right let me switch to modules okay great so we have our menu set up i'm an admin i don't see it because i've excluded myself let me just double check this and make sure it is for the correct role so i'm gonna impersonate john jason first he's a csm user he should not have access to this right i do not see a product owner menu up here for him so i can tell that that role cannot see it which tells me that my role specification is working so now i'm going to impersonate alyssa chinoy she does have the scrum user role perfect so you can see as soon as i log in as alyssa i do have that product owner module or menu here i do have the same ability to filter through and pin it to the sidebar if i want and the modules that i set up are here so i can just jump to those easily um this might take just a moment to load because the agile board but as you can see you can go back and forth between your different modules so this is a really cool feature you know if you're onboarding different like process users you know in the past you may have had to go in and tell them what's a favorite or they may have needed to favorite the things that they need the most you may have gone in and created a dashboard that has this stuff for them or just something kind of onboarding these different product roles with more of a manual process and with these new admin configured menus you can just go ahead and set up the things that different roles need right for them so they have everything they need at their fingertips um right when they log in um and you know they don't miss anything by not accidentally favoriting it or not knowing that it's there um this is just one really really simple example that you guys can kind of see all the different things that you can do with these menus i'll go ahead and get back to our slideshow here i think we have another poll brad um i'll let you go ahead and launch it while i'm sharing the screen here all right it's launched um so this poll is just the different kind of topics that you want to see um in our upcoming academy sessions perfect we got a lot of great input coming in so it looks like ui builder is pretty pretty uh popular i know we definitely have a lot of questions on things such as data resources um that you guys are just really interested in going more in depth on looks like how to configure different workspaces as a runner up there awesome so we will definitely gather all this information um and take into account for future sessions um for the academy and even like you know coe or center of excellence um documentation as well so we want to know what you guys want more information on so we can get it out to you i'll go ahead and end this poll i think we got a really a lot of really great um answers here thank you so now i think we'll go ahead and just move on to q a but i see we got some some questions coming in so we do have a good question here as far as um do you have to have a workspace to enable next experience is this mandatory um before you turn next experience on do you have to have it you don't you don't have to have a workspace to turn next experience on we encourage you to start using workspaces when you turn next experience on but you do not have to go through and implement a workspace to upgrade san diego you don't have to implement one to turn next experience on but really to get the full value out of the unified navigation header um you do want to start moving like i said there's tier one tier two fulfillers and agents or those process users over to a workspace so they can begin using those customized experiences but still are able to get to what they need in the classic environment by using unified navigation uh and then there was another one i wanted to hit on oh somebody has uh an enhancement request around filtering uh anytime you have an enhancement request you should go put that in the idea portal so if you go to the community.servicenow.com and click idea portal you should put that in but that is also something that we have heard in terms of filtering in the all navigator and popping favorites up to the top in that so that's definitely a strong piece of feedback uh that our product teams have heard so we answered some of these live um do we have answered live that we want to call out here yeah so one of them uh do you have a script checker that would highlight ui scripts that are broken by next experience so we don't have that uh i would say any global ui script you should examine uh and and test and make sure it works uh just because there's like how do you define broken or not uh from like a programmatic perspective we we kind of discussed when we were planning the uh the checker um you know what we would do there and so right now we're only kind of just surfacing yes you have global ui scripts and you need to check those uh what else do we have here um how would you set up different workspaces for different roles and groups um i can go ahead so so my take on this would be uh so for workspaces we generally have um you know we've got service operations workspace for tier one it agents we've got csm configurable workspaces so those agents you know should be using those workspaces and then individual pages in those workspaces can have variants and so i i would look into setting up page variants i would try to keep you know your number of workspaces smaller so don't try to set up a new workspace for every you know every different type of person if they're kind of doing similar things but yeah yeah i want to mention too if you're using app engine studio to set up workspaces during that whole wizard process you define the roles that have access to your workspaces and if you need to you know add more roles after the fact there are acls that you can go in and modify to add those roles as well uh we had another question around documentation uh there is documentation uh on our developer site uh for client scripting uh so the uh you know the client scripting you can do within uib uh is documented for the most part uh they're they're you know some things that are not documented because that's we always have some stuff that's not documented um one live um do you need to use app engine studio to create a workspace um no you do not need to use it i'm going to put an asterisk next to that you can create a workspace in either studio or by going through the modules be aware on this method you will get the workspace shell so you get the header in the sidebar but you will have to configure all the different pages that go into what a workspace is yourself we do have page templates that you can use to do that app engine studio makes this a really quick process by basically providing all that for you um app engine studio does come with its own licensing so please you know speak to your account reps but if you're looking to create a workspace experience for an app in five minutes that would be the way to go as far as using app engine studio all right i am adding a couple of links to some documentation answering one of the questions here uh let's see what else we have uh some good topic suggestions i'm just answering the one about i'm using the portal app shell for the request and today maybe we should answer that live we got quite a few questions about portal so do you want to answer that one live and then we can also just reiterate portal um what is the what's the question i don't see it well i can take it so the portal app shell that you see in aes that's a very specific department level portal so it is a portal that we've experimented putting on the new platform but it is not full feature for instance you can search but you cannot browse um the catalog is very limited um so we really require we really think that is a good use case if you have a very like department level intranet um where you're just gonna search and respond back with some some catalog items so or cards um so that is not a full featured portal it is only available through uib and aes but it is a very specific limited version portal as mentioned previously we're currently looking at our portal plans nothing will be released before our vancouver release and that will probably be like a v1 or an experiment to see how we do this and then there is really currently no roadmap as of today to fully re-platform portal onto this next experience we're still evaluating that and doing some testing now so utilize the portal app shell as an experiment very limited features make sure you're aware of what features are and are not available there and then the utilized service portal or employee employee service center is the is true portal right now as the enterprise portal and that's right and i would add the it's really more of a limitation issue not a like you know the portal app shell is not going to blow up on you or anything it's just really limited in what it does and how you can configure the menus and everything all right a couple of good topic suggestions in here um ui builder pages support web sockets for real-time data i don't know i i haven't seen anything on the road map for that i would grab that's another question what was the other one well ui builders support bootstrap it does not currently support bootstrap which is you know part of that it's not responsive to the experiences right now uh we are looking at you know how we would make it responsive i don't know that it'll be bootstrap it might be some other responsive technology or we may build their own i'm not sure but right now it does not support bootstrap also on the workspaces i mentioned uh you know trying to manage your workspace sprawl uh that's just more of like you probably don't want to create 40 workspaces because they're all managed individually and so you probably don't want to be managing that many workspaces so there's not a limit it's really more about think about maintenance and testing and all of those things as you're moving forward you know i think part of our our near-term goals for ui builder are you know doing making a little bit easier to use up front and also kind of reusable things and so you know just kind of be thinking about that you you really want to keep the number of pages and workspaces smaller because when we do come out with new things then you have to up level uh those those pages and experiences and i think if since you all have heard where we're taking this especially in tokyo since tokyo just went early access if you are planning to create workspaces from scratch without extending one of our licensed products please utilize tokyo to do so it will save you a lot of engineering and coding having to do that and there is there is actually i see you put you're answering it there is a question about utilizing next experience components on service portal and that was an experiment we were working with and actually our ai search is a macro component written in next experience that we wrapped in angular and exposed in service portal so we have done it ourselves we were evaluating releasing that publicly that technology we have actually stopped that experiment it does not work as well as we thought so um we don't i'm not familiar with the blog post you're talking about we don't recommend it so it's probably some type of hack that one of our lovely developers did we know everyone's so excited about that but we don't recommend that um i did want to go back to that workspace question real quick too before we get too far away from it um this is where the concept of variants and audiences is really going to come into play like you wouldn't you wouldn't want to create like a manager workspace versus an agent workspace um you could actually use audiences and variants to show different pages to different personas all within the same workspace so utilize that heavily instead of just creating a whole different workspace for a persona you know on your sidebar add like common elements that all users could use but then you could really you can get really specific with those variants and audiences as far as what you want to show on the page you can even use the concept of viewports we have a viewport component to where you could show it's basically a page within a page and that uses audience and variants as well so you can really show different kind of pages and experiences to different roles all within one workspace so you don't need to have multiple workspaces will agent workspace be discontinued soon in favor of next experience workspaces it is on the roadmap um we do suggest if you are looking into using agent workspace and you're on san diego to look at our configurable workspaces instead if you're on an agent workspace right now begin your migration strategy and have plans to migrate off we don't have any release specifics on when but there are plans to sunset agent workspace in the future just check out on any other questions that we may have so it looks like we have a pretty in-depth question on switching pages based upon different audiences and multiple variants i'm going to take that one offline alex that is more kind of a technical one um and more of a technical use case so if we cannot answer your question here um go back to this session on our coe because i will be posting comments to questions that we had the parking lot here um so just check back to that to see if your question has been answered and i'll mention you if you're on the community so you get an alert about it as well i i would add if you have additional questions uh we have posted the link to the next experience subforum and i know ashley and i both are subscribed to that community and uh we do try to make it a point to at least address each of the questions that come in um not as prolific as amanda i'm there i'm just not as prolific or quick to answer questions as both of them are the true experts we'll get back to you and and we want questions we track you know what questions people are asking us on the community on s dev slack and customer meetings we're tracking all of these things and that really drives what type of enablement content we're prioritizing which we know there's a lot of enablement content for us to create around both next experience and ui builder we're almost to the top of the hour here i guess we'll go ahead and close it down looks like the questions have stopped coming in if you sent me your information or put it in the chat here for the adoption program i will reach out to you shortly on just setting up a meeting to get your feedback to be on the lookout for next month's session i don't remember the exact date let me see if i can find that real quick brad do you know i probably should have had that up before starting this i think it'll be the i think we decided we're going to do third what third wednesday of the month yeah so whatever that works out too august 17th um so we are planning on some ui builder stuff and then after that what's new in tokyo um and then we are gathering books and different topics for future sessions so yep august 17th wednesday at 12 p.m eastern you can register for all the sessions at once if you'd like with the registration link and we will be promoting them on linkedin in the slack channel and other social media all right awesome well thank you everyone for attending really appreciate this for attending our first next experience academy and we look forward to speaking with you guys again in the future on different academies thank you so much bye everyone