[Music] hello and welcome to creator toolbox this is the servicenow show that helps you add tools to your toolbox hence the name and we have another one for you today but before we get into that let's do some quick introductions i'm chuck tomasi senior developer at a senior developer advocate it's early here and service now been here since about 2010 go back a couple of years as a customer go back even further and you get a lot of old history that really doesn't matter anymore hi everyone i am earl duque i am a developer advocate here at servicenow i've been with servicenow for about a year now but before that i was in the higher ed space doing development for servicenow for about four to five years thanks and uh my name is char lin i cover application lifecycle management in our platform product organization as a senior principal product manager we do have very long titles here um i'm based in kirkland uh i've been a service now for coming up to three years now hi uh i'm padma chavatikoti i'm the senior manager of the platform engineering at servicenow i joined servicenow as a software developer and i eventually took on the leadership role my team is located in santa clara i have been with servicenow from last four years um that's like so far my journey is going good thanks chuck for doing this thank you so much she's the rock star of this episode well with the introductions out of the way now that you know the players on the stage uh i say we jump right into it uh charn would you like to introduce what our topic is today and why we've come up with this give us the background and then we can turn it over to our rock star to show us around the neighborhood sure happy to um and we're really excited to share with you our feature for upgrade plans uh in the tokyo release one of the biggest pain points that we know is that customers had in their journey to upgrade servicenow is just managing upgrades across your many instances dev test staging prod coordinating with all your developers to resolve their skips manage your customizations punch them up through the instances as far as either update sets or applications in the app repo all that coordination and management for all of your work at the end of the day was slowing down our customers to being able to complete upgrades end to end uh and so for our average customer the fastest upgraders are taking about four weeks to upgrade still we wanted to see if we could cut that down at all uh so the top couple of features that we decided to deliver for upgrade plans in tokyo is firstly we want to help you be able to package your skips and customizations uh into global apps and app customizations so that you can more easily move them between instances you may notice that we specifically did not include update sets in there we wanted to help customers move to adopting app repo mechanics with that secondly we want to help you to be able to define applications and their versions to include in the upgrade plan so that you have one source so to speak for managing your entire list of deployables across instances and then lastly you can use that upgrade plan to apply to your targeted instance about to be upgraded and that automates and optimizes the installation during upgrades so you're saving time across the entire journey and with that i'd love to turn it over to palma to jump right into the demo thank you jan yeah so hello everyone so um the upgrade plan uh required different kind of instances there are two kind of instances we required one is like a builder instance another is the consumer instance so the builder instance is nothing but the developer instance where you actually all the application developers go and develop their instances the consumers is nothing but your test of the prod instances let me uh directly dive into the builder instances how you can build your upgrade plan on that so once you upgrade it to the tokyo version once you go to this upgrade central uh window where you can see there is a new menu got added which is like an upgrade plan you just click on that this instance is currently configured as a builder let me show you how can you configure your instances of the builder or the consumer so in the upgrade center properties page we have included this upgrade plan properties where you can configure your inst instance preferences builder or the consumer once you configure as a builder on the instance uh once you configure your instance as a builder uh that is gonna be locked down and you always gonna build on that instance all the your customizations you're gonna resolve on that instance and you're gonna build whatever the application you want to build so let me directly uh jump into the upgrade plan so how upgrade plans gonna be building um so uh to give you a background so once you upgrade it to for example you are upgrading from tokyo to the utah version so once you upgrade your developer instance you can go to your upgrade history and you resolve all your customizations for example you see on my screen i have 11 customization to review but i have can you hang on can you make the font a little larger oh sorry um is it better now much better thank you ah okay thank you so much maybe i have to do it on all the page uh everything is oh that's all right okay okay that's good yeah that's good yeah so as you can see uh here on my um on my customer customizations you can see i have i don't know a 4800 customizations on my instance and a couple of them are i need to review so customers in generally go go to these customizations and they resolve all these customizations manually and when they resolve all on in the developer instance they have to take all this you know update set or a customization package they need to repeat all these steps on the post instance on the consumer instance which is like a test instance or the production instance so upgrade plan is mainly focusing on automating the whatever the things you are doing it on the dev instance so the first step for the customer is okay go to the dev instance upgrade to your root ah okay now in this instance as you can see i already upgraded to utah it's already skipped scripted records are generated and my customizations assume some things are already resolved so once it is resolved customers can come to the upgrade plans page and they can simply click on the build button what what it is doing is it going to build a plan for the upgrades so internally gonna go and look it into i'm gonna just click on the build button um to explain what's going on um so when you click on the uh building the upgrade plan button it gonna pop up with some warning saying because our aggregate client works along with the app repository we need to have app repository because we are building all these customizations and we are publishing to the app repository as a customization packages automatically using the upgrade plans so this is giving a warning because uh on the dev instances developers might be have their local branches working you know uh they might have in their uh changes in between then we are just giving a warning to make sure you have a clean system so at least you can when you are because we are automatically publishing we don't want to publish your live changes so let me click on the build upgrade plan so it gonna take a while this build upgrade plan i'm gonna explain you what's happening in the behind the scenes so what we are actually doing is we're gonna go to the current upgrade history record we're gonna collect all the skipper records i'm gonna we're gonna group them into the different different scopes which it belongs to and we're gonna create a customization packs for all those customization records and we're gonna publish them to the app repository so while you are publishing uh if if for example all the customization uh all the customization in the global gonna be uh put it into the global customer a global application and some of the scopes might create a customization packs for that particular scopes and we're directly going to publish to that poster so this is gonna take a while i'm gonna show you uh the one i have created on my instance uh already um so to speed up our process it's this is the one which is getting created and this one is the previous upgrade which i have done so you can see here there are a couple of uh customization items which is already generated here uh you see this is a global customization upgrade plan uh this is the one which actually it's a kind of a group of the bucket where all the global customization is going to put into that global application and these are the other plugins which have the customization this is the action status automation you see there is a customization version already published to the uh repository and this is the application development 2.0 is maybe after upgrading my developer instance i might have i want to explore some of the new features on the instance for example customer okay now i upgrade you to bring in some workflow advanced feature okay i want to try that plugin customer can install those plugins on the dev instances upgrade plan what we are doing it you just install what are the actions you are doing on the developer we are as upgrade when we are tracking all the actions you are doing your installation your upgrades what are the applications you are upgrading and what are the new applications you are installing new plugins installed we are going to track them when we are creating the when you are doing this build process we automatically capture all that information and we are going to dump into the upgrade plan so you really no need to uh repeat those steps on the production on the production instance of the test instance uh let's see um this is still running um mama maybe this would be a good point for me to jump in and uh just highlight um what global apps and app customizations are uh so if you go back to your second tab um this is a question that i frequently get from our developer community what is a global app and what is an app customization because everyone's familiar with what a scoped app is you're familiar with what your scope is what your scoped app is but the question has always been well what do i do about all my work that's historically been in the global scope um or even the scope of somebody else's app let's say servicenow's app or an app from the store an isv partners application um and so throughout paris quebec and rome we delivered other ways for you to package that work into application let's call them containers or artifacts um and that's what you're seeing in the list here for upgrade plan items that obama just shared with you so the global customizations one is a global application that includes all of the global files that you can claim into that global app and this global app can similarly go through the application repository just like your scoped apps do when you publish them um from dev studio for example uh similarly uh you can also take your work in other scopes and pack them into app customizations that are based on a particular version of the underlying store application or the servicenow application and that too can go through the app repo so now all of your work uh scoped apps your google files your work in other scopes all that can go through the app repo as their own independent uh packages artifacts um specific versions and that is what you are listing uh in your upgrade plan uh to manage uh your work to deploy to another instance chart did we have to do anything prior to this with the with the global artifacts and claim them or was that done automatically by the upgrade plan step that's a great question and that's one of the best things about upgrade plan so prior to upgrade plans you would have had to uh do a little bit of work to claim your global files to a global app either via dev studio um where you open up a global app go to file add existing files and then you have to claim them one by one which is very tedious right in uh san diego release i believe it was we added a feature where you can select multiple updates that's global update sets and then take all of those global files and dump them into your global app so that made everyone's lives easier uh but with upgrade plans here one click button uh all of the uh skips um customizations related to those uh will be automatically dumped into a global app for you so even easier for you to start using global apps but yeah great question chuck another quick question padma you were showing us upgrading from tokyo to utah which is is still a bit in the future we're ahead of ourselves but that's going between major family releases i assume this also works for doing patch releases if you're going tokyo to tokyo patch 3 for example yes it's going to work for the patch releases also this feature is included in the tokyo so i'm just showing you the demo from tokyo to above next release which is going to be the butter okay but we can't use it to go from san diego to tokyo because no we cannot use it from san diego to tokyo it's gonna be from tokyo and ebon there's incentive to get to tokyo people operate today i mean even speaking on that i think i remember hearing a stat about what the average update set way of doing upgrades how long it usually takes and what we're hoping people can get to do i can't remember how how much time we think we're people we want people to get saved by switching to upgrade plans so do you have that number again charlie yeah so uh on average our fastest upgraders who are mature adopters of automated testing or perhaps have just fewer customizations that they have to go deal with resolve skips for um are still taking about four weeks to complete the ndm upgrade so from starting uh at your dev instance for example and then finishing with your broad instance it's roughly about a week to go manage coordination with all your different dev teams and be like hey you know we've upgraded this instance go resolve your skips now package up your stuff and do update sets and make sure they don't conflict with each other deploy them to your next instance and then it's very high friction to make sure that all your different teams are not stepping on you just toes while you're going through uh that kind of process so here we're really hoping that the majority of that working coordination only has to happen on the dev instance as you're preparing your first upgrade plan afterwards it should just be a matter of applying the same upgrade plan um across your other instances and maybe uh some additional skips um will be surfaced and you can redo that work in the dev instance uh but this should really cut down on the amount of time for those subsequent upgrades so we're really hoping that customers can go down from say four weeks down to maybe two weeks for their uh complete upgrades um and hopefully even less if if they have a uh a more well oiled and coordinated team handling all those customizations and skips if you're an hourly employee you're out of luck if you have no customizations it could all go happen immediately someone's thinking i'm gonna get paid for four weeks worth of work [Laughter] your paychecks has been cut in half oh no you can spend more of your time doing things that are of more value to you and your organization okay so yeah i think our build upgrade line our plan is finished i think it took around two minutes for us um so once it is done uh it's gonna give you the information what are the uh what are the uh what are the like applications were published to the repository what are not able to publish to the repository you can simply uh look at the view details and it gonna have all the details of what are the application it was able to successfully published and this is using the app repository right if you have a multiple dev instances if you are doing multiple customizations um so you have to make sure the same customization packs are installed on the instance otherwise it's going to give you a conflict one conflict error message because it's saying i already i already have the same application different application customization already present on the repository if anyone using the customization packs they might aware of this like one developer the app repo is like where it keeps all the customizations it needs to have a unique id uh to push the customization packs so and each application can have only one uh one customization pack you cannot have multiple customization packs so this is the conflict you're gonna see it so for example in my case i have some conflicts and i have some successful cases so let's go to the upgrade plan and see what are the application it was published boom you can see all the applications so far all the customizations were packed into my global customization pack and my application customizations are packed into these particular uh particular applications and along with that on my drive instances i have installed my brand new features which is like these these are my customer applications i install on my dev instances so that automatically and i install this new feature called azure development 2.0 that is also automatically get added to my upgrade plan so yeah this is basically once you build the plan we collect all the activities you have done and we automatically gonna put a configuration for you and it also captures what questions you install what customization version i supposed to install on the other instance okay so so far i have built the upgrade plan so once i build the upgrade plan now my job is to there is a uh there is a another options on the upgrade plan i forgot about to explain which is that refresh for example i go to my uh corresponding upgrade history uh and i like after building the plan i went to the upgrade history and i resolve my more some more customizations so you can simply resolve those customizations and you can come back to the upgrade plan we just refresh it so we automatically gonna get packed and it automatically gonna publish to the repository for example you see here i have these customizations uh which i'm gonna update um for example i'm picking this one let me uh see the related record i just want to make sure this is a global record sorry it's taking time no problem i think um we have some good questions in the uh happening in the chat too that we might want to highlight um i think we're going to cover some of this but we're getting questions about our uh skipped record skipped upgrade records are included but are the remediations as well and uh yes they are um fixes to the skips are also included into the upgrade plan okay you can go ahead i will get through more of the questions in the chat uh later yeah sure yeah this is already uh in my global upgrade customization upgrade plan uh global record so i'm just gonna simply go ahead and modify something uh maybe in the advance and just put some comments i'm gonna just save its record okay so now i'm just gonna come here and i'm gonna you're gonna give the same warning uh on the builder uh while you are building using the same warning just make sure you have the latest code available otherwise we'll try to publish the unfinished code so i'm gonna refresh it gonna do the same thing again what it's behind the scenes what's happening is it gonna pick the from last uh when i build the plan to now it gonna be all the latest updates happen on all the application listed here and it automatically pick that delta and it gonna pack those delta related applications and it can automatically publish to the repository i'm sorry okay so this is also going to take a while um we just because it's two minutes time every time build it gonna take two minutes we can take more questions if yeah i appreciate these as stretch breaks and going to get some water i think um other things too it's hard because i don't want to oh i don't want to step on your demo but people are asking good questions in the chat too some people are asking does it also grab other stuff like uh configuring future new features and i believe uh it records a lot of that including the installation of plugins too and that helps that be part of your upgrade plan so it's not i was at a customer i was at different customers for years and upgrades were always uh it was a kind of a song and dance across multiple people across multiple departments to get these done but um like just within the developer team upgrading something and then fixing it and then now we have a list of new features and plugins that we want to activate and then patching those and working on that and then we have to replicate that next instances for our um our consumer instances for our test instances and then production all of that is simplified now and it's such a more straightforward way to it now i remember when i heard this released us for the tokyo release notes and i read through it i was like what why do they make these things after i'm not i stopped being a customer i do the same thing where was this when i was a kid [Laughter] gotta love software and how it always changes and gets better yeah yeah i think i think we are done so the refresh upgrade plan is done um so it took her on uh one minute is the same thing you can go to the view details see uh what are the things i'm just closing the uh directly going to the upgrade plan um so i have modified this global customization upgrade plan um so let me just refresh this page so it can automatically uh you see here there is a new version of the upgrade plan uh the global customization upgrade plan is generated and the new version is published to the requested so this is how you build and refresh now you once you are ready you can publish this upgrade plan to the repository so i'm gonna click on this button so what it is internally doing it is it's actually gonna create a upgrade plan global application for you and it gonna automatically publish that collect all these configuration put them in a global application and publish to the repository so i didn't show you that before that it was like it was global now it actually changed it to upgrade plan global application yeah so now all these records were attached to new global application and it's already published to the application repository so this is how you do it on the builder instance this is how you build the upgrade plan um once your plan is ready it gonna publish to the repository now okay your builder is done now you can go to the uh your test instance or your consumer production instance you can directly install this plan before upgrading so i'm going to show you how to install uh on the one of the instances i hope this is not locked up log me out let me just refresh okay okay so let me go to the upgrade plans uh and there is a return button you can click on it which can take you and show you the new plan i have published there so what question did it publish it published 1.0.2 and this is the upgrade plan name i'm going to just copy that so this is the consumer view once you go to the consumer you're not going to see any build options here you're going to see only the review option so once you click on that ritu it's gonna take you to the my company applications uh with the upgrade plan so i'm gonna directly give the name so this is the application uh sorry this is the my upgrade plan which is i actually uh published on the other repository so you see um oh i think i have to refresh let me just refresh because i just published the 1.0.2 so i need to pull down from the store so now this is the exact same plan i have published from my uh developer instance so i can install this uh one thing you have to note it down is you have to install before upgrading to the utah so on the consumer you're gonna retrieve the plan you're gonna install before the upgrade so upgrade can use your upgrade plan to uh install your application you install your whatever the configuration you have configured and whatever the customizations you have given we're gonna automatically install during the upgrade and we're gonna automatically resolve all your customizations so before going to this i just want to show you one quick thing before installing i want to make sure i show you this another feature so i think everybody are familiar with the upgrade previews yeah so uh see when i go to the utah i already previewed once and you can see here i have total uh number of skips it's showing if you are upgrading from your current tokyo version if you are going to the booth you can see the total number of skips it's showing i have total number of nine skips is available here so what upgrade plan is gonna give you is once installed installing the upgrade plan this block gonna be changed that's the magic i'm gonna show you let me just install this first so you install the upgrade plan before you do the upgrade i guess that's a good good reason to call it an upgrade plan it's not like a patch you put on after the upgrade that's that's nice okay now my upgrade plan is installed um let me go to my upgrade plan once i can show you what view you can see here on it in this instance boom you see uh it's actually install the upgrade plan and you see different view than what you are seeing it on the builder you can see there is something going on here it's representing the state ready to download i'm downloading so what we are doing it is uh as soon as you install the upgrade plan we're gonna read all your configuration and we're gonna download all the sources you already published to the application repository on the builder instance we're gonna download and we're gonna make it ready for the upgrade to consume it because why we don't want to go in between the upgrade to grab all the sources what you are giving to us because that can cause you know some reason the app store is not available during that time or there is some network network issues then you're gonna get some unexpected failure during the upgrade uh we don't want that kind of a situation that's the reason what we are doing is before getting before uh before making sure you are uh making before upgrading making sure all your sources are ready so that's the reason you see all the states here some of them are downloading some are the ready to download and some are automatically marking it as already okay boom all your instances are all your applications which we have published on the developer instance now it is ready on the consumer instance there is another another thing i want to highlight here is and you see the versions you can review all the versions as administrator you can go and uh review all your configurations correct or not some reason you found some bug in one of the customizations or you know one of the application you want to stop installing so you can simply just select this and you can just mark it as a fox then those will not get installed during the upgrade so and you can skip them to do it in on demand after the upgrade or some other reason your entire upgrade plan itself has some problem uh and if you want to disable your upgrade plan during the upgrade you can go and just disable your upgrade plan we're not going to pick that during the upgrade so now my consumer everything is ready so when you uh one thing i want to highlight when you install application as i mentioned it's automatically getting downloaded right so automatically getting downloaded it automatically creates a preview also for you so right now if i go if you see uh previously uh it was actually some previewers there but right now it's getting calculated so this will give us the information about what what kind of like skips are automatically resolved and uh and what are the skips i might get reverted if i don't provide the customizations so you're gonna see that data in a few minutes uh once this preview is done i think we're almost done yeah we're done i think i maximized it so the alignment is no bad but so you can see um there are like total records it's saying uh with the upgrade plan there are like seven automatically getting resolved but there are two uh two customizations which you did not provide a customizations for me if you don't provide a customizations because servicenow is sending some customizations for you then we gonna automatically get reverted that's what the information it is providing that's a to review to be reverted by upgrade if you don't take any action if you see this kind of a situations you can click here to view what are the files it's getting reverted so you can see here uh i have updated these are like assume like you have a customization mismatch between two instances right so assume this is the situation we have created here on the test i have extra customization my dell does not have these customization in that case we are saying we're going to automatically revert if you don't provide the customization for that so your job is you can go to the developer instance make sure these customizations include into the global application and you're gonna publish the new version and get the new upgrade plan like you can just simply publish the new upgrade plan version and upgrade this version so these these versions gonna be getting upgraded and come to the preview to see that magic automatically get resolved so that's the suggestion we give if you get into that kind of a situation i think most of the customers have that kind of situation because they have different customizations on different instances in some some cases so this is the uh this is how uh you you will preview and you will install the upgrade plan and your upgrade plan is ready to consume by this instance so once you kick the upgrade plan sorry once you get the upgrade so it can automatically pick this upgrade plan we're gonna install everything whatever mentioned it mentioned in this configuration during the upgrade itself what is the advantage of doing that during the upgrade itself is so you know for installing all these things the schema artist is the pain if you have multiple if you have like millions records in the task table and couple of them are adding some customizations to the task then it gonna take forever a lot of time to do those altars so we actually uh uh using this way you can actually club into one alter including in the upgrade itself and it can automatically apply your customization and once upgrade is done you really no need to resolve anything as as the preview is reflecting here i automatically resolve this so upgrade engine is taking care of marking your scripts or result because you already provide the customization upgrade upgrade plans so uh this is the pre-processing uh three steps for the upgrade once this is done you're gonna configure you're gonna um you're gonna go to your uh maybe your one of the uh high instants and you're going to configure your instance to upgrade to the next version so i'm planning to do that right now or to show you exactly how the upgrade is kicking in and how you can see the results just give me a few minutes i'm sitting here setting it up to kick off the upgrade we had a question uh if for clarification if you are preparing the upgrade plan and it shows you skips for the upgrade and you don't take any action on it action on it what will happen to that skipped um change on the consumer instance will it continue to skip or will it revert back to out of box it will revert back to the out of the box we're not gonna escape it's like a force reward right thank you okay i'm almost ready um just eric's follow-up comment to that was if you've got some of those low priority ones that you know people have been traditionally lazy about going i don't need to pay attention that's just a you know form layout or something you want to be sure that you put some actions behind that okay okay so i have kick off my upgrade um let me go to speed up the process so i'm gonna go to upgrade monitor and on the right instead select our instance oh the dreaded transaction oh the counter is done okay so i have just uh scheduled my upgrade this was the previous tokyo patch serial upgrade so i'm just clicking on so it can kick off my upgrade you can take a few questions sure we have a good question um from ishan uh if you when we do these upgrade plans and we get it all the way to prod uh and we had some remediations for skip records will those records again show up on the next upgrade um with an upgrade plan or will we were or will it know that it has already been remediated and not listed as a something to review so upgrade plan is tied with each upgrade so if you don't provide a plan for that particular upgrade we we're not gonna automatically resolve your customizations so if you don't know upgrade plan no automatic remediation so you have to uh go and fix it manually okay but i think this question was more like if i if i did a i'm upgrading from tokyo to tokyo patch 3 and i said yes i want to keep this form layout that i did to the incident form for example does it remember when you go from tokyo patch 3 to tokyo patch 6 or do i have to re-establish that from an autobox baseline it says hey i already did this once when i went to patch three do i have to do it again in patch six and then again in utah i didn't change the form in any way since you know december of 2018 but yet it's still recognizing is it going to keep nagging me about the same change over and over for every upgrade plan or is it going to remember somehow and decrease that list over time to just the deltas that i've made since the last upgrade so upgrade plan the global application what you see it we actually copies everything all the customizations but as a upgrade engine we only calculates the change if you really have a change then only we're gonna load those applications if you don't for example you installed previously global uh global customization pack version one now you are going to the path six you are using global application version two then it gonna calculate the delta if there is no changes we're not gonna apply them that's optimization already exist in the upgrading there's a time saver exactly okay you see now uh i think uh my upgrade one of the note already uh kick off the upgrade so once you kick off the upgrade you can see uh my i have a schedule upgrade and it also have information hey you are scheduled upgrade to so-and-so version and we are using this upgrade plan to upgrade your uh instance so you can click on that it's going to take you to the same version so that next process gonna take a little bit time um so before that i can jump on to the how the post upgrade action is going to look like so on my test instance i already installed my upgrade plan and i already upgraded it to show you the post post activities okay so this was the my previous one this is installed this is the consumer view and you can see there is a history record which is representing when when last my uh upgrade plan was consumed so if i go to that it gonna it gonna inform you okay is it in store is it have some issues or if any like some reason um one thing i i forgot to mention i think on this thing about these states uh in the uh in the uh upgrade plan items these states represents it can give you errors also for example you have something like entitlement issues or you have some licensing issues if you have some kind of those address we gonna automatically reflect here saying hey you don't have an entertainment for agile development 2.0 then we're going to say that error and you're going to see that corresponding status message before upgrading we are giving you uh we are giving you a chance to go and correct those errors before upgrading itself so uh you can for example you are on this instance maybe on the production you already installed this application water that is maybe installed long back so if that is already installed we're gonna automatically say hey this is already installed i'm not gonna consume it's during the upgrade that kind of state is you're gonna reflect here and the similar things gonna reflect back into the history also currently i have everything success there is no failures i don't have failure scenario but uh if you have some kind of a failure installing maybe due to some dependency issues or do you do maybe some uh some uh some licensing issues or something if you if you if you're not resolved during the pre-pros uh pre-upgrade stage then we're not going to solve those things during the upgrade so it's gonna still gonna reflect those errors here currently what are the plan i have everything is configured everything is installed let me go to the upgrade monitor to show you what exactly showing up here okay so uh once it is upgraded gonna reflect what upgrade plan i have used here and this is the box which gonna reflect hey i have already resolved these 15 skips but i have reverted this one skip because you did not provided me the customization for this that's what the information you are we're gonna provide you on the upgrade monitor so if you go to this uh you're gonna see that reviewed and retained auto resolved by upgrade plan uh that's a comment you're gonna see uh and there will be a um information about uh like global these are auto resolve from like this is a group by this all these applications are auto resolved from my global customizations upgrade plan so if you have maybe like uh like in the customer i don't have on this instance some customization packs but if you provide some customization packs if it's automatically getting resolved those you're gonna see them as a group by uh list of what are the packages automatically getting resolved and the reverted one also gonna show up here and it gonna show reviewed and reverted replacing the customization with the base version and the resolution is not provided in that clip now that's the information you're gonna see it here um that's pretty much the entire upgrade uh plans from building to the consumer and yeah once you see this this means for the post activities we have taken down lot of button for the customers to repeat the after upgrade those post activities and upgrade is automatically getting consumed and it automatically getting resolved your customizations yeah that's just putting it lightly too it really is saving a lot of time oh my gosh this this reminds me of um when i was younger i lived in a very old house and we had fuses because at first you know upgrades are are kind of pedestrian they're not the most exciting thing in the world until you realize how much work you're spending on them you know but as i mentioned when we had fuses where if if you had an electrical problem the fuse would blow and then you'd unscrew the old fuse and look around and see do i have the same amperage and the same brand and put it in there and you'd be back up in service and it was it was kind of a pain in the neck and then later we upgraded to circuit breakers you know pop pop you're back in business it saves time that's that's kind of what i look at here is once you start using upgrade plans you're going to look back and go what what was i doing you know that that spending all this extra time because i know i know there are a lot of you out there that will not adopt this right away and you're going to stick with update sets and you're going to do the same thing that's been working for the last 16 upgrades and god bless you eventually you're going to get to a point and say this is taking too long or your boss is going to say we gotta make this shorter this is your weapon for that so i encourage you to look at it adopt it review this video again when you get to the tokyo your your first upgrade from tokyo to something else and and and make note of how long it's taken i know there are uh who was it kim at texas a m had a chart of how long their upgrades were taking and you know as soon as she started employing one of her new features they went down keep track of those times and and compare this is how long it took pre-tokyo this is how long it took once we got upgrade plans in place and i'm sure you're going to see a significant change i feel like even just showing that you're able to demo full upgrades with actual clicking of buttons on screen and not have it take hours it shows even that how much it's improved and how much faster it is because i don't think before this we would anybody would be able to accurately demo upgrades and moving update sets and all that stuff accurately and without losing people from like a single screen yeah we showed a few when upgrade center came out we had a tech now episode on it and we showed a few things that were you know important in upgrade center but we didn't do the actual upgrade so padma you've reached a new level of of uh accomplishments congrats this is a great thing thank you thank you um actually we had a lot of questions in the chat but your demo actually addressed almost all of them um organically so i don't think we have to backtrack to any of those previous questions let me make sure yeah and thanks corey for hanging out and answering a lot of them too yeah we had a question uh what happens to the global app after the upgrade is complete does it stay in the application list or does it disappear no it will stay in the application list okay so you could end up with an application list that's fairly long thank goodness the next experience has a search filter mobile app or the apps that are globally sourced apps show up i'm like oh that's true where is it so yeah global apps so the google apps will stay in the application repository where they're published and will be then installed for consumption on a consuming instance but the global apps will also stay in your uh upgrade um plan list itself so in both places unless you you know manually go delete it off of either the plan or from the outpeople do they appear in the application picker from from the top uh do you mean the uh the app manager view well on the top menu bar you've got you know your update set picker your application set picker yeah it will appear there yes okay it should appear there uh and it will also appear in your uh my company applications um page as well uh if you wanted to uh you know in between upgrades add more files to that global app uh publish it again to the app repository or even use it as part of your ci cd pipelines with our csd apis um that's all possible once you have it um in a global application another good question from connie she asks is this is this standard is this an add-on is this uh the answer is comes standard when you upgrade to tokyo you get upgrade plans even better my favorite price no no excuse to not use it all right it i think we've run the course thank you once again charn for the information and padma for the beautiful demo and earl for driving and watching the questions that's going to do it for this time we look forward to seeing you again real soon on creator toolbox with more exciting tokyo information earl raise your left hand this one that's when i said left it shouldn't have taken anything to think about it still it's hard it's not mirrored like on zoom this is part of our tokyo calendar and if you want to find out more we are in the tokyo season rolling out a lot of new features creator toolbox breakpoint podcast all of that is by topic and by calendar over at devlin.sn tokyo so you can find out more get links to things we've already done set your calendar for things we haven't done yet and we'll keep rolling through this into november so we've got lots lots more coming look for those favorite features and set your calendar appointments aside and we will talk to you again real soon once again thank you charn thank you padma thank you earl and thank you viewer for hanging out with us we're gonna boogie on out of here then take care bye [Music]