[Music] hello and welcome to live code happy hour for august 5th 2020. i'm andrew barnes and we are here at servicenow and we are going to do some live coding on the show today uh we've got some friends with us here the usual suspects but let's go ahead and do introductions starting with brad hello my name is brad tilton and i am a developer advocate with the developer program here at servicenow i have been uh doing some sort of development on servicenow for about 12 years and been an employee for the last four-ish and today should be fun awesome thanks brad and chuck hey my name is chuck tomasze senior developer evangelist at servicenow been here for just over 10 years and a customer for a couple before that wonderful day awesome thank you chuck i'm andrew barnes developer advocate here at servicenow uh coming up on my two year anniversary here in a couple of weeks i think uh been on the platform for six years uh cus had a couple of customers and an implementation partner and really just enjoy in building on the platform and engaging with our developer community uh and so super excited to be here with you fine folks today um let us introduce our beverages of choice today all right so it's summer pretty hot here i have a carboc viva cella it's like a salt and lime beer it's pretty good that sounds good good summer drink a little tequila in there what do you have chuck i went back to the well i am back to the moosehead grapefruit rattler that i had a few weeks ago so it was very delicious i saw the nice tall pink can staring at me and went that'll do and i am drinking the last one of this uh vendor the edmund ost's sour apricot peach i think i've had this one on the show um all all of the ones from that all look the same to me and they all taste wonderful so i'm really sad that this is my last one and i don't know when i'll get any more because i can't find them anywhere [Laughter] so on this show we do live code development none of it is uh prescripted uh we um don't do any pre-canned demos or anything so we take uh real cases that we want to work on um and then show them to you so while we have a goal and objective for the show and we even sometimes reach it um the how we get there and how we problem solve through it uh is the fun part um and is what i think is the my favorite part of the show is the showing of how we get through the things when they're not working exactly right um because a polished beautiful thing at the end is nice but it doesn't teach you a lot if that's all you see is the the polished beautiful thing at the end today we are um in our paris early access time so the current family release uh is orlando but the early access is paris and we are going to do uh some not super developery work today we're going to do uh some admin work uh because we don't have we don't have an admin on our team it's just us developers and so we have to do some of our own admin work and what we're going to do today is subprime instances so we operate our own instances for our program and we've upgraded one of those and now we need to go through the upgrade uh you know post upgrade checklist steps so that we can get ready for upgrading our production level instance um and while we're doing that we're going to show and highlight some of the improvements in paris we'll probably mention some of the other ones that have come along as well that are available in paris um while we're doing that uh so anything else we want to cover before we hop into there um yeah let's uh today but these fine gentlemen chuck has got a new podcast called breakpoint and brad was his first guest on breakpoint and they're talking about resources for becoming a servicenow developer right you get started tell us a little more about it and how to get it chuck yeah it's a discussion with brad and i had a few days ago how to get started as a servicenow developer so if you've got colleagues out there that are admins or developers on other platforms this is a great discussion it's only about 20 minutes so it won't chew up a whole lot of your time if you listen like me at one and a half or two times the speed good luck listening to me because i tend to talk fast [Laughter] going to sound really fast but you can find it the easiest way is a bitly link sn dash break dash point and that will take you to the main page on our hosting provider from there you will see where it is on apple podcasts so you you go look directly it's now listed only apple google spotify you get it you get your podcast source of uh choice the major players are out there if you've got a directory that you want to see it on let us know i'm sure i can submit it so all right at least add that bitly link to the description of this uh youtube channel for everybody um maybe one of y'all can throw it in the chat but i'll make sure it gets in the description as well um after the show so great response we socialized it this morning so thank you to everybody who's been retweeting that and subscribing and downloading and listening there will be more every other wednesday smash those subscribe buttons [Laughter] i don't think i've ever said that on the show t-shirt but it was that was just for funny uh because it it makes me laugh because nearly all those youtubers out there are like go and smash that subscribe button right now is that what we're supposed to do now okay no no please don't uh so i'll go ahead and start uh screen share uh and we'll we'll get going through our upgrade process i'm watching closely because i just upgraded a couple of instances too all right so uh hopefully uh things look good uh brad give me a little thumbs up yeah awesome so i have our uh subproduction instance loaded here and what i've done is we've already scheduled and run the upgrade so this is sort of that next step is after the upgrade is completed i want to come and look at the upgrade summary in the upgrade monitor monitor you'll notice over here once you upgrade to paris that the upgrade monitor has gotten updated to say legacy and there is a new area called upgrade center in which the improved monitor has been placed if you load the legacy page it'll give you this little helpful message that says hey this page still works you can use this but come on over here to the new experience so i'm going to open that up so that we can sort of look at the differences between those two things and i assume it's probably just setting a user preference to say which you want to go left or right um a user preference to when you say click here to switch to the or maybe maybe it is just a redirect i'm not sure yeah that just opens the page okay so um and uh ultimately this old legacy upgrade monitor uh will go away and you'll just use the one under the upgrade center that we're going to check out today so you can see here we've got our new upgrade monitor um it uh right off the bat you may notice that the name of the upgrade uh gets the nice name version difference nice so so that's nice that it human actually uses the human readable uh name version of the upgrade that's uh super nice right up off the start um it shows you the the duration which is on the other one as well just and and i'll show you a little bit uh you know in a bit something more interesting that will be in that area i really am a fan of this new area of aggregating the documentation that that they think i need for this upgrade so these three links here um you know view the fix problems the personalized release notes and the known air portal for the particular family and patch that you've gotten is i think a really nice uh nice thing because i want those and i go and find them myself every time but it's nice to put them all there together for me the next thing you'll notice is we've got some nice dashboards here um to show us a a few interesting bits here the total record changes um is not super important like i never pay attention to that number because unless it's egregiously high or egregiously low like if i saw it say the number four i would be concerned or a million um but anything else i'm like yeah whatever i don't care you scrolled by a little button on the right i did and we're gonna go right back up to it in a moment okay we're gonna spend some time on that button all right uh so it shows me a little summary of my skipped records so if you've not ever done a servicenow upgrade the skip record what that is is service these are uh when you get an upgrade what happens is uh servicenow pulls down the upgraded version to your instance and then does a comparison between all of the application files in the upgrade and all the application files you have and it does a comparison a diff to see which ones have changed and then of the ones that's changed the next step it does is it says hey is the uh customer uh has touched this um and i can't remember the exact tag uh like uh there's a there's a field name for it but basically it's customer has touch this so don't don't mess with it during upgrade time and that happens whenever you as a developer go and modify any of the servicenow provided application files that record automatically gets flagged as saying hey don't mess with this upgrade time and then that is what generates the skip list record is the ones that you have modified and that's changed from servicenow since the last time you upgraded so you can see we don't have that many we only have seven in this instance because most of our stuff is completely custom apps we group them in priorities so depending on the type of change um and the uh application record type it will have different priorities you can see all of ours are our low priority uh seven this is a brand new feature here this skip records by product um so we're detecting which application file a or for a given application file which uh product that is associated with and in the event that it doesn't know which one it's associated with it will associate it to the uh the plugin so it'll tell you the name of the plugin if it doesn't know you know say that it's itsm or um itbm or nowplatform it'll just give you the name of the plugin and then uh one of the coolest things and we're gonna see this some more um and when i go press that button is it lets us know now whether or not a script field has been adjusted or not and that just fills my heart with joy having the number of skipped records that i have reviewed in my servicenow career has been a lot of them a whole whole lot of them and for many of the application file types i really only want to know whether or not the script field's been modified because if it hasn't i don't care about that skipped record for some of the application file types and a different kind of person a different skill set is needed for whether or not there's been a code change or not right like the unable to determine category [Laughter] so uh that that is a really exciting to me is that code changed versus code hasn't changed so that i can do the assignments differently and then the last thing i'm going to point out before we go look at the scroll up again is one thing i want to point out is we didn't have any automated tests that are running automatically here but when you're doing your upgrade whatever your testing process is do that first prior to your upgrade so do your fresh clone then do whatever testing process you have whether that's atf or selenium or humans or whatever it is record the results of that test and then after the upgrade redo your tests yeah because it's really easy to say after the upgrade oh look at all this stuff that broke when it may have been before the upgrade and so we've we're surfacing the results of atf's here on the upgrade center page if you have any that will run from that so as chuck pointed out we've got this uh new thing that i scrolled right past which is the skipped records and there's a skip record vtb and vtb stands for visual task board and that's going to open us up a visual task board to manage those skipped record tasks so there's a whole new uh record that has uh been created for paris that corresponds to an existing record and i'll show you what that looks like so if i go over here to the upgrade history and then we do upgrade for this one this is the way that i've often approached this problem in the past yeah and so this is the upgrade um history record uh where i have all of these different categories of skipped changes to review excuse me and then whether or not they've been reviewed or not the customization's unchanged so this is things that you have modified but servicenow didn't change in this uh family version so you don't necessarily need to review them so these are these are application files that you have modified but that that servicenow didn't change in the from for us from orlando to paris and for you it'll be whatever family version you're coming from to going to and so this record if we go take a look at this table this is the sys upgrade history log table and we have generated for this vtb um an equivalent so a paired record on a new table that i'll try and remember the table name but it's basically sys history task is is what it is so it's a task entry for every one of these skipped record these system upgrade log entries we created a task for them and they're paired together and they they they will stay in sync so if you make a change on one of them so if you if you have your dev team uses the old way and half the dev team uses a new way they stay in sync so the this vtb will show you uh the same thing all the time which is which is nice um so i have um for the purposes of some screenshots earlier this week i actually uh put these into those were not real results yet yeah i hadn't actually reviewed any of those but i wanted to take a screenshot and so this is what it would have looked like uh just right after the upgrade without me having touched it um and oh one thing i didn't notice was i i forgot to assign them all differently i did this in our production instance but i forgot to do it here in the subproduction which is uh remove a bunch of these admin rolled folks that shouldn't have it aha that's why they all showed up and so that list is populated with all of the admin entries wait a minute hmm i saw fred and kristen and a whole bunch of others they must be in a group or something is there an upgrade admin go check good oh fred and see what he's got i think i i it looks like i tell him no not necessarily i think that those got populated so i think i did fix it but those are populated at the when the board was created okay so when i said i i did it in production i didn't do it in dev i i think i lied i think i did it in both and this list is populated um when the when the vtb is created so i could go and remove these people but i don't actually care so i'm not going to um but what you can do here is if you haven't used vtbs uh one of the great things about them is when you're assigning these tasks you can just you know grab a person and drag them onto it so brad gets to go and review this one um and i can use these labels um to help me right which um so i can do it by product or in our case maybe i wanted to do by does not include code or includes code and that just narrows down the application file types and then there is the one with the for the code changes i think you can use the switches on the right too yes so those those work the same way so we can toggle those on and off oh no that just that turns them on and off and it disables them does the filter so i can filter my list and say oh okay all of these that are uh filtered poof andrew gets them so sam has a question he says if is the scoped application will that be in the list of skipped records that's a really good question and no a scoped application will not show up in my service now upgrade history list where it will show up is here in this cis upgrade history log are the yeah those are the the records i want the upgrade history so if i go to the upgrade history for a scoped app when it gets updated whether or not the scoped app is from the store or from the internal app repo it it really doesn't matter the source its entries show up in the system upgrades table so if you install a plugin or a scoped app it will and then update them the update will show up here as its own entry from the old version to the new version and will contain the details of that version upgrade and can absolutely contain skipped changes and so when that could happen is when you have a store app that you have modified and then you update that version of the store app you're going to get skipped entries and you need to review those just the same as you do for upgrades for the whole platform you need to do those for updates to versions for scoped apps excellent question though that is an excellent question because i think i've been victim of that in the past like hey i just changed this in dev published it and installed it why am i not seeing all of my installed things and so now we're ready to to to do the work so let's do the work uh so we've got this uh task and i have been assigned this task so i am now going to work this task so i'm going to open up the record that has been assigned to me to work and i'm going to review it and so this is usage analytics count configuration hmm let's go resolve the conflicts so that's going to open up our diff window it's going to say i'm not authorized that's hilarious apparently i don't have the uh authorization to to fix this but let's take a look at the difference anyway [Laughter] so here is on the left is what we have and here on the right is the the new one i i believe that this is the new one yeah now up here it says customize and this says base system i don't i don't believe those those are the correct labels so i suspect that this left one is what this record exists right now and we can go check that so line 17 uh we'll see if it contains a add aggregate or a new query let's go let's go verify that so if i go uh to this previous screen and then i where is my handy dandy go to record where's the go-to record oh that's gonna make me sad [Music] i'm gonna open this in a new window then because i believe that that's a uh that's a ui action that's just not rendering for me no where is it and i thought it was right here to get to that record yeah maybe it doesn't exist i don't know what i'm talking about right yeah yeah it was normally it's right oh uh it wasn't on the resolve conflicts maybe you have to go over to the yeah i go to the this one there it seems like a uh a thing i'm going to ask for to fix usage analytics count it's a good share app idea for anybody for a second one i think oh he's got some skipped error stuff too no it's not showing at me no related record oh yeah it is i got i saw two of them and i i was sad okay line 17 has an add aggregate oh so it is it was labeled well it said customized and i don't really care for that title because isn't this the new updated one on the right so they both have at aggregate right but there's like four lines missing yeah so the the new updated one is the one on the left apparently okay which is not normally the flow i expect i i expect to see what i have on the left and the new thing on the right right old and new and they're telling you they're telling you this thing on the left is like our this is the system one and then the thing on the right is your customized one right it is a little bit but this is new this is new stuff it's it's now the system but it wasn't before uh so um i'm going to uh i don't have it's a read-only one uh so i i can't uh can't do anything uh other than just revert it so i couldn't merge this one for example right uh so i'm going to revert to base system so let's do that which is only which is kind of a merge right because the only difference was it had four new lines yeah effectively it was a merge yeah so your v i oh you could have reverted from there too revert debate system yep i could have from here i just you know was already on that other screen so i've done that one yay and you can see my vtb has been updated to see it's over there um one other thing uh just because it's funsies uh we can raise the priority because these are lanes because the incident list layout was terribly important i wonder i wonder how do i hide this yeah i'd lane i want to hide these that i don't actually have anything for just because it's bothering you can't use them how do you bring them back i have no idea how to get them back now i want to know how i get them back because that's funny how do i get them back you'll never see them again they've been deleted from the database they're gone all right so let's uh review our next one so uh instant list layout guess what i do with those review and retain because i'm not even i don't care what the new layout is i've customized it and i'm happy with the layout i've got sure uh a property all right is that your text search engine ts that version why would that have been modified by anyone other than the other by anyone let's see what it changed i'm guessing it's just like old version to new version yeah that's our zing search engine so it changes the value from algorithm it changes it to aspen and currently we're on calgary i don't think i'm gonna be uh touching this i don't know you might have had some some things that went wrong in calgary so i'm going to decide uh to retain that one the things you discover when you start looking close uh defer component attribute i definitely mess with some attributes let's take a look at this one i want to go look at one of my other instances that hasn't been upgraded to see what that property is well it oh that hasn't been upgraded to paris glide.ts glide.ts.version is that what it was yeah mine's set to calgary too what do you know on orlando um whatever that means why don't i have oh skipped air yes you had some skipped errors what's the error and why can't i see like the record i feel like there's details i'm not seeing on this entry i want to get to the the history entry yeah it seems like this flow could be a little more optimized i don't know if that's an implementation thing or an education thing on our part yeah i that's a good point like maybe i just don't don't know [Music] uh that was attribute skip there and component attribute so you see i can handy dandy get to the task here but not to to this record it doesn't contain any more uh details but let's just go take a look at the record and see who modified it and see if i care continue updated by tectonic oh really good good job tectonic i'm gonna leave that one alone then so my disposition for this one is leave it alone and this one i think was one of the error ones as well yeah we're gonna right so does that mean it will show up as an error on your next upgrade as well uh good question um so what will happen for sure now is that i'll be able to see this disposition for next time what i did last time so if it does show up as an error i can one i could have noted in here like i could have put a little uh comment like i have no idea why this errored nor do i care post but i'll take it and then uh next time uh what will happen is uh when i open up this entry next time uh oh it doesn't show it to me here oh good it just took a second to learn excellent i was disappointed and then it just took a second so uh what what you'll see here is next upgrade uh whether or not that's a full family or even a patch that this entry shows up and generates a task it will show me this existing one here in the related list and so i can see what i did to it last time and um and so this is brand new so this concept of the disposition history is brand new so previously um there was nothing captured to update sets during your um uh the disposition uh of the actual like entries didn't do anything what you did uh was captured so for example here in the when i open up one of these and i i click the ui action to say like revert to base system the reverting that application file to base system is stored in an update set but what isn't stored is that this entry in the skipped list that changed its resolution from not reviewed to reviewed and reverted was not retained but now these task entries those are retained and uh put into update sets and so you can combine that update set of the the decisions and why i did them plus the actual actions you know the what as all together yeah but what is what is this what is the upgrade details related link bring you to on this page i have no idea i've not clicked that one oh it it takes me to the record okay so that smooth things out a bit nice it does so that that makes me happy we can uh cancel that yeah we can cancel that request and you even called it out you were like maybe we just don't know and so that was actually generally the answer is we don't know and so let's take a look at this last uh system property and uh so for the most part system uh properties uh i leave them as they are yeah because you may have modified them and said hey it's the way i need my system to run uh resolved and yeah we're going to leave this this one actually doesn't even have any changes in fact it says hey there are no differences found uh so that that just means we modified it and then put it back at some point oh so could have been something subtle as this well so we tagged it for a change and then we reverted that change back to the original but it was still the application file is marked as you have modified this so servicenow is not going to mess with it so we could revert this one back to base system if it gave me the button but it doesn't seem to give me that choice you know what else would have been fun is to run a health scan before we did our upgrade too oh that would have been fun uh so i'm going to say i'm gonna uh review and revert that i haven't done it yet and uh to be clear sliding these tasks does not execute those ui actions so reviewed and reverted like revert to base system that ui action that sets this task to review and revert it moving the task to reviewed and reverted doesn't actually execute that ui action okay does that make sense yes okay you still i don't know if it makes sense or not but this is telling me we understand here's the work to be done we've all reviewed everything now you go through the ones that you want to revert you go through the ones you want to merge and theoretically by the time you're done with all right you're done so i could have had uh you know one of the team members come and and choose their choices and then might have someone else come and review them before they're actually executed yeah right so the reviewed and reverted we might have someone actually come and check again that those are the the decisions we actually want to do and then come and open these up and click the ui action to actually revert it so that that is something that you could work out as a team um especially you know for higher priority ones higher risk ones is basically the priority list here is is about risk so fives ah probably just go ahead and whoever touches these go ahead and resolve them but like priority ones you might have someone tasked them originally like we'll put uh we'll put kristin to task it to make a first pass and then our architect or senior team member actually come and say yes we're actually going to do that yeah you could you could do your assignments any way you feel like based on priority or based on what lane it lands in or yeah nice um so that is the upgrade history which is great so what we should be able to do is i created an update set and so we should see those both the revert to base system entries and the the task details here so we've got our upgrade details um and we've got modifying that so we actually did revert this one and so there's an entry for that right [Music] yay i had in here what i expected to have in here i like it when i get what i expected and previously the only thing in this update set would have been this bottom one because that's the only one where i actually use one of those ui actions to revert to base system or merge or whatever and and then the the details of what i did to those uh didn't get captured or passed along to my higher level instances so i couldn't go back in time and see hey what did i do to this last time and a lot of us exported that stuff out and saved it so that we could do that in the future but we didn't have a good way in the platform to do that until now so this is really exciting for me um so we have done our review uh for our upgrade so we ran our to i ran our tests um and we have done our upgrade summary review uh and checked out all our skipped lists and so now i can close that update set move it into our next tier instance and then uh run the upgrade on that and then apply that update set and i should be good to go from that aspect the next and last thing that i wanted to like really highlight um that's new in this upgrade center isn't something we can actually do um but i want to show it to you anyway which is upgrade preview which will look fairly similar to the upgrade summary after you execute it and what this does is it will uh connect with hi and ask hi hey what instances are available for this instance to upgrade to so whatever you see as choices when you go to high to schedule an upgrade that will show up here and we we're on the highest version right now so there are no choices for us to preview to but you could choose um both a patch you know so you can choose the next patch or you know two patches forward if those are available and the next family release and then you hit execute this go button and what that does is it will one it'll give you an estimate of how long it will take so based off of other customers who have gone from the version you're on to the version you select it will give and some information about your instance it will give you an estimate of how long that upgrade will take and then after it's done the preview calculation it will give you a very similar screen to the upgrade screen the upgrade summary screen so it will look very much like this the upgrade monitor screen the summary one because it's basically doing the same thing it's just not executing it so it's performing all of the same actions it normally does during the upgrade except for it doesn't actually commit to the database any of those changes it just says what it's going to do and so you'll see how many skipped records you have the priority of them how long the upgrade should take roughly how many changed records and and so you'll get an idea of how long it will take you to triage and uh actually you know plan for your next upgrade um it's always interesting when we get one of these enhancements for upgrades that i can't actually use this yet yeah when i when i saw this one uh i thought it's going to be really helpful for customers that don't have many instances like especially the ones that have two or three and you know it can be kind of difficult to isolate one of those sub prods or you're only sub fraud and get it upgraded so this kind of cuts down on that upgrade time because you can say you know i'm not quite ready to upgrade dev yet but let's look at the preview and at least see where i'm going to get affected the most in this next upgrade and so uh to that point brad one of the things that i did when i had a bunch of instances is i would just say even before i'm ready to do the upgrade i would just clone one do the upgrade and then check out the the impact so i'd run my atf's and look my skip list and sort of gauge how how how uh how likely it is i could do this upgrade soon or not and then just quickly revert that clone back without really impacting our process but if you don't have you know a bunch of instances um then that's harder so if you only have the two or three instances that a bunch of customers have yeah it can be very difficult to just say i kind of like to get a you know a gauge in the wind of of how uh how much work we've got to do for this upgrade and and this offers that up um what i was going to i was going to look at something based off of that around the history oh so like i said it's sort of a little weird when we do an upgrade that uh and improvements the upgrade process that you don't necessarily get that immediately um and so it's a little hard to describe that to other people so when this customizations unchanged was added um i think it was i feel like jakarta i think so no yeah it was in that time period yeah but it wasn't useful until the upgrade you did after that upgrade because uh because it took a a snapshot at that your first upgrade after that that enhancement was added it took a snapshot then and then um allowed you because previously all of these uh skip lists would have been over here to review all 135 of these every single upgrade even if servicenow didn't change anything for those it would show up and we'd have to triage those and and figure out which ones we actually had to review um and so when they added that i was i was so excited um because i had built something to do the same thing and so i was so excited to have that in the platform for everybody but it was a little hilarious to explain this is going to be really useful to you your first upgrade after your first upgrade that's after kingston [Laughter] you got to start so this upgrade preview will be very useful to you the first upgrade after your paris upgrade yeah whether that's a patch or your quebec upgrade right and if you go from uh you know orlando to uh to quebec it'll still be your first upgrade after quebec maybe we can show that to you sometime in september we can come back to that later after we get patch one online yeah and and we can come back and visit that uh so that's that's it for me that i needed to do um for our our production upgrade so i think i'm ready for that uh is there anything else that you guys saw that you wanted to to touch on uh or you want to drop out of share because i accomplished my goal which was get myself ready for the drink take a drink you have one more question from sam in the chat he says when we are when are we going to get health scan as part of the upgrade also can you talk about health scan and how you handle the report or is this going to be another happy hour episode good question um so health scan um so there's two components to health scan there is a engagement with our professional services customer success team on um really diving deep into the details of the health scan of your instance and helping you figure out a plan to resolve them and then there is a a lighter level of that which is to give you some indication of the score of the instance and i believe that it's slated soon on the platform to be able to run on demand that score level one yeah and so there will be an api for that uh that you can invoke uh either through a scheduled job a ui action um a business rule um a precursor to an upgrade um you know at the end of a sprint you know for a sprint review however you want to implement that you can do so because it'll be api available for you to access that health scam area but we can't share a lot of it right now because it's not something that's in the the system um today and unless i missed it in paris release so awesome i will stop my screen share uh and so y'all have done more upgrades than well at least more families gone through more families than i have but i have i have been through some some monster upgrades on the platform with uh 20 20 000 application file skipped reviews wow yeah i think my first upgrade was uh fall 2008 to winter 2009 back when we named them after the seasons uh but what's funny is i i don't think i've actually been through an upgrade in probably i don't know like eight years so [Laughter] looking at sometimes looking at the upgrade functionality i it doesn't really dawn on me you know how helpful it is until like now like the vtb you know all this extra vis visualization of skipped records and then being able to come back to it in the next upgrade and figure out why you skipped you know i think i have a new appreciation for some of this uh upgrade functionality in paris after having watched the little demo here it it feels very analogous to like when we got guided app creator or studio onto a lot of these things that accelerated and and made it easier and automated a lot of the things that you did manually i mean just remember making a table when you had to go into number maintenance and set up your own numbers you know you can do 45 minutes worth of work in about five minutes now that's an improvement that's a better experience for everyone and we want to shorten those upgrade life cycles so that you get to the next release sooner you get the value for your investment and you play with a whole bunch of new toys as a developer so you know win win win win so tomorrow i've got my blog on the developer site developer.servicenow.com for the upgrade center improvements and some of the resources that i link there for folks to use is we've got some upgrade checklists and best practices from our customer success center um what else is is useful there i think the most important decision i ever made as a platform owner was no new features so when when doing my upgrades i actually like to limit the number of new features that i enable at the upgrade time and separate out those new features whether or not it's new uh you know core platform feature or a new feature in one of the the software products i like to hold off on implementing those um but still have them planned still be ready for them and they're still moving along the pipeline but i separate those out from the upgrade and really drip drove at the customer i work at to a a non-event upgrades being a non-event so and and we actually got to that point where uh we went from something like a two-month upgrade cycle um and time and process to three weeks nice end-to-end from from when we decided we were going to do an upgrade to it's deployed in production um so that's the upgrading the subproductions running the testing planning communications everything end to end was three weeks and we lowered the communications we sent out um because there was less need to notify people because there was less drastic changes and then post upgrade we'd have some big feature release upgrades or releases so that new feature that we wanted to do the upgrade to get that would be two and three weeks out from the upgrade so that it could be separated and prioritized and treated uh as its own important deployment and really separated out that this is an upgrade issue versus this is a new feature and really helped our customer base and our support teams really understand the difference between those two things and gave a lot of clarity to oh our upgrade process is actually pretty good we were all just introducing lots of new things new features and experiences and things which you know drives that that costs customer service time right so and and then that makes it seem like upgrades are scary because we have an increase in customer service but when you say i had a new cool release of this feature and that had associated customer service you're like oh well it's a new thing that makes sense it's gotta it's supposed to be that way um and it made our cut our our users happier um i think and from what we evaluated them that they kept that separate so that was that was one of my best uh best plans i think and really made my upgrades a lot easier uh because making them a non-issue and then you can focus time and attention on that new thing you're releasing and make that a separate experience and it really helps a lot uh so cool that was awesome uh anything else to share upgrade wise sage advanced and who knows so i i love i love getting the new features so i like upgrades because then i can't plan to release new features uh and i like the new features i've really enjoyed my i i don't think i have to share too much about it i these are good i need to find some more of them brad how was your drink today yeah my karbak vivacella it was excellent i'll give it a solid four a solid four nice how about you chuck still digging the grapefruit rattler i'm giving that a four as well nice and uh these haven't changed they're still a four five these things are fantastic good job charleston you're a winner those are delicious well thank you for joining us again i want to uh say that we'll put the the link to chuck's new podcast um here on the show i'll get that in there tomorrow uh and we've got the upgrade center blog releasing tomorrow um you had a blog on tuesday right um brad i did i had a vlog on automated test framework uh and the new features and in paris which skewed pretty heavily to custom ui tests and page inspector and just kind of improving the experience there it's getting pretty well flushed out now atf is so it's a it's it's pretty nice uh pretty nice product now now we need some now we need some test steps for workspace i think there are some right are there i i believe there are i'm pretty sure yeah so you need to do a custom ui thing for workspace i'm not sure custom yeah i know you can do it but that might be custom i don't know in my the drop down that says you know is this service portal or is this a ui page it doesn't include workspace so it's not there yeah so yeah that drop down got more options still not there well there's a custom one but uh it doesn't so the custom ui stuff still doesn't support uh like shadow dom right uh which there's a lot of workspaces so but there are some workspace steps i'm 90 percent sure all right well thank you everyone who watches this uh today or later we appreciate your time um and i'm glad i'm now tomorrow i'm upgrading my production instance with with confidence so i've run my tests i've done my skip review i'm ready to go uh so thank you for joining us everyone have a great day