readings everyone and thanks for joining us for today's uh platform fundamentals Academy we will be covering best practices for upgrades this session is going to be host by o yinka oini he is my colleague in the platform outbound team and we are lucky to be joined uh by two panelists who are on the inbound team responsible for these platform tours tools um so yeah looking forward to a good session um ask that uh any questions you have um please please please put them in the Q&A um it can be difficult to keep track of everything in the chats uh but but feel free to use the chat as well of course but please put things in the Q&A and we will uh be sure to answer those intermittently as as necessary and and be sure to have a try to answer all of those by the end so with that uh y I'd like to let you uh take over thank you all right thank you John hi everyone um like John said on the Alon PM for umm which is application life cycle management and with me here I've got goind and Pad Ma so P ma is the engineering manager for upgrades and Goin is the inbound um PM for upgrades so we've got all AJ that can actually help you with issues or questions you might have but today we'll be we'll be talking about the best practices for upgrades and um as we all know um we are a couple of months away from a couple of weeks away from uh um G release for zanu and um some of you preparing to to upgrade and also some of some of you guys that would also want to upgrade to to Washington DC this information will be would also be very good and helpful for you in your Bri cycle so without much I'm going to go ahead to talk talk about what we are for today so the whole point of this call is to talk about best practices for upgrades planning and executing um so I'll just go right to trade um during this we might be talking about some things that um that might that might be on the road map or would be on the road map and we don't want you to make um any purchase decision based off of this so this is our safe AB notice and um we we got different tools and features within the now platform tools we've got ATF upgrade Center application manager so this these are just the things that can help you properly and efficiently manage your your instance or um your application as the case may be so these are tools that you can find available that can also help you with every single thing you need to have during your instance all right so um today we'll be talking about why upgrade planning is critical we'll also be talking about key steps in planning we'll also talk about testing and execution basically we'll just do high level discussion about this and we want this to be as interactive as possible which is where we have p and go there so any questions you might have um you can indicate them but it would be nice to go through all the deck before the questions can start coming in but if you have questions in in between you can just drop it on the q& a so we can have that documented and and we can respond to that after I'm done presenting so um what's important like what why why is upgrade planning important um some of you have been have been doing an upgrades for a long time and you can as well agree with me that some of this things listed here as you can see uh one of the reasons why planning is important the first one being it helps you ensure system stability and performance and by what do we mean by this basically regularly upgrading your instant can actually help you achieve optimal instant performance and the second one being you would prevent issues related to outdated applications when you when you are upgraded or when you have your instance upgraded you have the latest tool to to use or you have the latest module to work with that way you prevent issues that are um that are ass associated with outdated applications the second one is mitigating risk of disruptions um you want to properly plan this in the sense that you you want to reduce the risk of downtime there are situations where upgrading upgrading your instance would actually affect um how users are interacting with your applications and the lik you want to avoid this which is why we typically talk about upgrade planning why upgrade planning is important it also helps you ensure smooth transition with minimal impact on users like I said users don't like it when they have downtime and disruptions so this is just it will feel like I'm just saying things you know but it's it's important to reiterate this and let users like you understand why um upgrade planning is very important then the next one is um you helps you late new features and improvements there are some things we're working on within upgrade and um the the the more you are on the latest family release or depending on your grade cycle the better you have access to these tools and these tools will help you ensure that your upgrade cycle is as shorter and as efficient as possible I'm going to go next to the key steps in upgrade planning um the first one we basically tell customers as soon as possible once you have access to the release notes try and read them as as early as possible and the reason the reason why we say this is because it helps you understand theix the features and the fixes in the update in the release like you want to understand how this will impact um your applic or how this will impact your customization so that's why most times you tell customers um review your release note as early as possible and this will help you identify changes that might impact your instance yeah it's it's very important to to review your release note the next one is assess impact once you've been able to review review the release notes and see the changes that my um that might um affect your your instance it helps you evaluate applications that that are valuable like for example you want to ensure that oh if it's going to affect one of your customizations this is what you have to do in in place and these things have to be documented um by assessing your impact also you want to determine dependencies and inations that need your attention and these are all all the things we we often tell customers to do um once you you've done the first two step review releas note um assess impact the next want tell customers is oh you also need to develop a plan and what's this plan how do you want to go about it um outline detail steps for your upgrade process I'm sure some of you guys are are are very good with this already so you you have all this steps um planned and properly documented you also need to set a timeline and allocate resources and one one thing I try to tell people um you basic you you really can't measure what you can't determine what you don't measure like for example let's say for example your last upgrade cycle it took you like two months if you don't have be documented and set a timeline you wouldn't be able to to measure progress so when you set a timeline and you allocate proper resources helps you understand oh where uh where can you make some adjustment to ensure that your upgrade is faster and and better um you should also include contingency plans like for example if you come across any potential issues that was not documented having a proper plan is also beneficial um for for this um um during the course of this webinar I'm going to share a link for the upgrade planning checklist and this is what we we typically tell customers to use like it's it's a it's a very long list that helps you ensure that every single thing is is um is well noted and and and documented so um to the next one so let's talk about testing and execution um there's no someone has their Androids um John I think we have Patricia has a question can we um allow her ask a question yes uh I'm work we're working on that so we'll get the answer back to you okay all right good so um for for testing on execution there's no um upgrade without testing and this is where ATF comes in um this is not ATF call so I'm going I'm going to um limit the the things I talk about ATF so basically um for for testing execution you want to ensure that you have a cycle in in in your mind like like from this Loop you can see there's a loop when it comes to texting execution the first one is you create a test plan and by creating the test plan you define the scope of the testing you also include critical functionalities um by doing that you should also create test cases and set your success criteria okay um if this if if you are creating this test cases what will make this test successful what are the criteria I need to look out for to ensure that oh this test is is acceptable or or as passed past our criteria second one is always and always use a surpr instance for for for testing so um clone your prod to your sub do your testing on your sub then the next step is oh you follow the plan the plan you documented earlier that you this is how you want to um ensure your upgrade goals follow that plan and monitor and address issues um I want this to be as interactive as possible which is why I made sure this slides and this deck are not as as voluminous as as possible so now I guess we can move on to the q& a to ensure um questions are un said and Patricia um if if you'd like uh I think we can have a uh a live uh Q&A closer to the end um so either place your question in the Q&A uh panel and we'll answer that as we go or make a note of the question we'll try get to I think we can allow them talk right now okay sorry some of our some of our panelists have different sort of styles but that's fine if you if you'd like to talk now that's fine yeah I think we well we're at the end of the of the slide we just want this to be as interactive as possible answer our questions concerning upgrades as much as possible sure so Patricia do you have a question find you participants Patricia um I'm gonna allow her to talk yes yes can't find you for some reason oh I'm sorry I I didn't mean to raise my hand I didn't even know that I did I must have been changing some of my audio so sorry for interrupting okay that's fine on and uh and our our two guests panelist Goen and P are going to help us answer our Q&A questions so uh uh what what would be so uh uh Mahir asked a questions like what is the best way to track track down the impact of the upgrades on various applications so do we have a way to do that uh yinka the to track the applications want to answer that sure I'll hop in hello everyone my name is goind uh I'm one of the inbound product managers for the upgrades team so pja and I do a lot of the product development for all things upgrades so as far as addressing this question for the future State I'll answer that first and then I'll I'll walk through what we have for the present we're currently working on redesigning the entirety of the upgrade user Journey such that it'll be a lot more guided but also help you very clearly understand the downstream effect of all customizations you're making and have already made on your future upgrades and the way in which we're going to do that is at the time when you're doing your planning we're going to basically distill down the key highlights from the release notes for you and look at your most used applications and based on that say these are the reasons why we believe you should be upgrading and these are the issues associated with a future upgrade that we expect based on the customizations you currently have in place so that is in the pipeline as of today we have a few things to try and help with that we have uh as you might have seen in Washington uh there should be an area on the leftand nav which will label all high-risk customizations so it's basically a table that will take you to high-risk customizations those are customiz ation that we believe are most likely to result in a ski record at time of upgrade and possibly even would go further to result in uh you needing to roll back the upgrade if something's really really aai um but more likely than not just going to be a skipped record so we have that table right now um and then in addition to that we also have uh the same messaging that we talked about in the last platform Academy if you sat with me and Adam Stout in that one as well where we are basically providing these friction tracker uh messaging so that every time that you go to edit a file if we believe that it'll result in a skipped record uh we're going to surface that to you and walk you through whether or not it's best to make that customization make that customization with ATF tests around that or rather deprecate an existing customization or choose not to make a customization new so that's a lot of words to say that we have some Solutions in the near term uh but a very extensive redesign coming uh for the future releases you can look at that for the Z or the a release excellent and I believe that this may this may help address A's question which was does service now have anything on a platform to identify items customizations that need to be reviewed that will be impacted by the upgrade but not all customization so I think he's asking um will it help you identify the things that might be a conflict versus just identifying everything was customized yeah I think that the future State we have that for sure uh in the current we are we have the high-risk customization table um and that's probably the best you're going to get right now okay great so Ed had a question about testing um are you using ATF or test management 2.0 or both yeah um let me take that so for for testing we typically um recommend ATF for all forms of testing because this helps you with mtion testing and we as we are always adding more features to help you expand your curve rate for testing so ATF is what we would recommend for for testing great I also want to add on one thing John to my last response I realized I missed the most important part of the upgrade process which is upgrade preview uh I think upgrade preview will surface to you a lot of your most high-risk customizations and your expected skip records as well oh awesome that sounds like an awesome feature and so yeah I think it's a related one um uh although I believe it's subtly different from just kind of the questions we had about SCP records um Anonymous attendee has said that we are doing and reviewing skipped updates sets every upgrade the problem is is it best practice to use an update set to capture um if we revert to base or not if we made some changes and we get to upgrade again service now is recognized and its custom when in fact they had down they had basically it sounds like they had downgraded use an update set to downgrade to a previous non updated version but still is identified as as a custom I think by default update sets treat it as a customization I can understand that your use case when you revert also it's picking it as a customization yeah customization I think right now that's how the upgrade engine works I mean anything inserted why update sets treat it as a customization so we understand your use case I think maybe we have to take it back and figure it out you know how can we do it better there I yeah I remember back when I was an admin I would I would say okay look I yeah you're right we don't need to make this customization or we change it so we would just find the older version revert back to it and add that record to the update set and I guess the hope would be that it would it would realize that even though it was deployed by update set that it wasn't you know it was treated as as not a customization after that uh yeah it's another good question I think this might uh be more of a process question is it okay to involve our stakeholders on early testing on the first instance like if we do it on Sandbox then Dev QA and prod so how early is too early to bring in our stakeholders for testing I I don't think there there a standard um response for this but what I say it depends on all your processes basically but we would suggest that um for all your testing and you should ensure all stakeholders are involved like let them like get all the requirement get all the success criteria you you would need to ensure you like this this this test is successful or this test pass passages so yes you need all your stick to be involved when it comes to testing great thank you um Anonymous has a question again it's back to the skip items and I think you might have answered it Goen um there could be a little subtlety to this one and uh just back to saying hey we spend a lot of time with skipped items to review them and then how are we going to minimize those so um it sounds like we're coming up some processes but is there going to be a way that's actually going to Ed the number totally so I'm actually or go for it I think I talked over someone no I think it's it's me only going go ahead gotcha uh so I was actually responding to Jenny via the chat who had the same question I think a little bit lower in the queue so we're currently actually in the process of Bringing Down the total number of ski records and that's done through a few different ways I think the first way that we'd love to highlight is the fact that we''ve done a very big change in internally in the way in which we develop software now here at service now and we have a basically a Tracker Where We Are servicing to our senior stakeholders and Senior leaders all of the teams that are making the most skipped records for our customers and trying to encourage safer development practices so that rather than creating changes to existing functionality in a way that's going to break people's customizations or result in additional skip records we're now extending functionality or introducing new files in a way that is hopefully going to bring down the number of skip records and lower the skip record count for our customers so that's the first thing and hopefully you'll begin to see that in the most recent release and then future releases as well brilliant brilliant I love that so we're mining our own data to figure out what the root cause of these is that's brilliant I love it exactly so that's the first way the second way is that we are actually making use of the skip record rules engine so I don't know how many people here on the call are already making use of that but the big win there is that you can basically think of it the same way you do uh a Gmail rule or an Outlook rule basically if you can say if something exists you can then perform an action on all things that fit that that type so for example if you want a certain type of skip record let's say priority five to always be autor resolved you can do that with a skip record rule so one thing that we would encourage people to do is that if there's a certain type of skip record that you want to autor resolve or a certain type of skip record that you want to Auto assign or something of that sort you can make use of that with the skip record rules engine and we're actually doing that internally as well uh there's certain types of skip records that we don't think are worthy of being surfaced to all of our customers but they are today so we are actually going to be using the skip recer rules engine internally to try and sort out some of the ones that aren't super important to our customers excellent excellent uh so this is a question from Todd he's uh it's a good question too actually haven't thought about this um uh with more more apps uh being moved to the store is plugins instead of being like family releases uh is there a way is there a recommendation on how to manage plugin updates during the uh upgrade process uh I can take up this um so on the upgrade preview feature we are planning to this is like a future thing we are planning to include the application versions what is coming in currently in the existing Washington release itself um upgrade monitor showcase the what are the applications were modified this release what are the applications were upgraded to what version uh all that information is presented on the monitor um but in the future we are planning to include it in the upgrade preview also so before the upgrading itself you can see what's coming in thank you [Music] um so we've got a question um uh we got a question um uh again I another question about Skip sorry that one's already been answered so look like that one is a duplicate um excuse me that uh another question is is um uh are the script record rules themselves captured in update sets no not currently okay yeah they have to Import and Export but right now we are not capturing in updates okay great um sometimes when previewing records from niach again um when proving records it Flags records are skipped even when there are no changes and highlight script fields in blue indicating changes although there are is no changes I guess this could possibly be related to what we talked about earlier um how does that mechanism work how does it know if something is a is A Change Is it is it basic on date and time or is it looking at the contents of the record no we look into the CIS update XML uh that is like customization uh truth um so if customer modified that any record we capture into the sis update XML that's the truth of the customizations from there um for the upgrade the changed or not we actually collect the hashes for every release and we keep it on the instance um so and we read those hashes hey if the payload hash is changed then we we see that hey this is changed then but you customized it so you have to review this because I am I am pushing the change also from the servical point of view so that's how we recognize what changed or not I see interesting I did did not did not realize that so uh Luis has a question um perhaps if you'd like to you can come off of mute and and perhaps ask it live uh Louis um or I can read it for you um but it has to do with the upgrade plans I think it be great to have more attendees voice questions so if you want to come off mute and talk about your question be great to have you guys talk yeah this was kind of long so it might be better if you could uh explain it Lise hi hi okay um well regarding the upgrade plans thank you for for for the session and uh I was wondering about the upgrades we tried this in Washington to use upgrade plans because we thought about it as a very good um idea but um we tried it in three upgrades and uh and we had some problems with it I don't think they um I don't know if they are if they are recommended practice already for the upgrade plans to I'm talking about the plugin upgrade plans not planning an upgrade as you mentioned yeah yeah so uh can you um can you explain a little bit um yeah I understand what you're talking about upgrade plans but what is exactly your question we when we did the upgrade on on the pre-development in the pre-production environment MH we ma the skipped records to the upgrade plan okay and to the upgrade plan application okay and then they created um Company applications okay for the upgrade plan but then we installed the applications in the production environment and the application brought um change it some many out of the box uh files and and move the files from Global to the new upgrade plan application yes which was which was very strange for us at least yeah yeah go ahead and the skip yeah and the skip records were not moved on to the production so we had to to to do the skipped records again as we did previously before having a plans so my question is well we didn't see any value on it so that that's that's why I'm asking uh I think the upgrade plans feature is meant for the who are actually using the app report Route like who are already doing the ACT to development who are already using the global applications all those things are if you are already adopted but if you are using the traditional update Set uh it's like a big change for you so adopt it um so uh because upgrade the way it works is it collects all the customizations from when you started this instance to now maybe if you started 10 years back it going to collect all the customizations and it going to take it to the production so if you are if your instances are not sync you have a you run the upgrade plan on the development instance they are not exactly duplica of the production you're going to see these kind of issues that's the first point and the second point is when you take it to the production Skipper records are missing means on the production you it might not have installed some couple of applications so on the subro everything is open you can install you can try and everything works but once it goes to the production um it required entitlements and Licensing that's one part of the issue and the other part we have a couple of defects related to taking into the production some applications were not installing we have fixed those things in the Washington and Vancouver um so that's what I can tell but it might be something instance specific or some other unknown issue you might have it on the instance uh first upgrade is very challenging Louis with using the upgrade plan if you are a traditional way of upgrading is the update set but the second upgrade should be the faster why because you already done all the setup and gone through all the paint so the second upgrade is the simpler creating and moving the stuff to the other place as I mentioned it captures all the customizations it's not only the one you modified in this upgrade upgrade plans meant for collecting all the customizations and taking to the production it works at the scope level so it's not work at the file level upgrade plan I hope I answer your question um yeah I was wondering if if it is a recommended practice right now uh if you're traditional update set it's not recommended to practice you are like always using the update set to copy the changes from one instance to the another then it's not anywhere instances are out of sync no definitely not no we did the Clone previously but thank you very much for your answer I understood yeah yeah all right um thank you P John so I think we can go to the next couple of questions on the Q&A sure thing um one question was asking about how do you uh uh record the rules um and I think Mark had a good idea which was that you could create an application file and the other idea was whether you could use a data preserver both of those sound like um legitimate approaches uh for something like this yeah so what we have one uh one more question from um Anonymous attendee um do we have a checklist activity that needs to be performed by the CIS admin live during mids server connections integration connections working fine credentials Etc so I not sure I quite understand the question here perhaps whomever posed this could come off mute and maybe give us a couple more details yeah or you can just raise your an then we can make you come M does uh [Music] um yeah so I think we're I think we're getting close to the end here um M here had a question again I'm not sure I fully understand it uh by uh any means can we get information about the major highlights like dications or role changes or any other changes the upgrade will impact functionality of existing applications so I guess I can hop in there John yeah so here that's speaking back to the redesign that we're doing when we are trying to create the what what we're calling internally to be bespoke release notes but what will actually be a kind of a value proposition if you will of exactly why it's worth upgrading with distilled highlights from the release notes one part of that will be us walking you through the deprecated applications in order of which applications you use most so if we see something that's will be deprecated that you often use that's something that will be highlighted explicitly to you sounds good do you want to sorry do you want to talk about the customization table I think some folks are having issues finding it uh let me uh find that table and paste it in the chat okay good so um Christen Jones um Roberto Brightman we going share um screenshot of those of the table you asked for um the new question does all this advisement apply to moving from ui6 to next experience or is this generally for moving to new family release um I would say that this isn't specific to ui6 next experience um that's its own um and you can go on um we have a a center of excellence on the community for next experience in the upgrade and there is actually a tool that will help you evaluate uh the next experience upgrade if you haven't done it yet um so that I think is outside oh Scopia yeah yeah that's outside that's outside yeah they have their own kind of questions and issues the nice thing about next experience of course is it's a kind of a one time deal in terms of like you making that upgrade but yeah there's go check out the next experience Coe on the community and they've got some tools and advice for how to make that transition yeah so Patrick this is strictly for um Family Rel upgrades any more questions guys this is the time to talk to folks that helping you with the upgrad so the more questions you have the better we've had a lot of good question so far thank you all yeah and I've learned a lot so that's good too yeah I would highly recommend all questions not to to put M's horn for her but she is Miss upgrade like all things upgrade she knows all the answers so highly would recommend asking questions here excellent she's a busy gal so it's hard to hard to track this exactly thank you so I think I have a new one um so we had an OB o defect that caused us to skip Washington other guide date variable assignment issued um this sounds like something you might want to create a case for um go you want answer this yeah I'm not sure if we can answer specific to this but if you haven't created a case uh you definitely need to and we need to know about it right and I hopefully you have already but if you have not please please please do so and then check with your account team and make sure that they get they get this resolved right you shouldn't have to skip this is not to do necessarily with our upgrade uh processes we're talking about here but we need to make sure that you don't skip uh releases because of things like this so please and P just posted the so for folks that are asking about the customization table she said you have to go to upgrade Center menu that's where you find the iris customization table yeah there is a left navigation um we have added in the upgrade Center so you can go through from that in the upgrade Center left Nom unication you can find that highrisk customization these are the these are the files which are actually uh shipped by the service now very often shipping so which can actually add the risk to your upgrade because we are modifying and you are also modified so those kind of the files you can see there so is available only from Washington by the way so is it Washington has a question I it's kind of similar some of stuff you talked about but uh reverting to out of the box how do you avoid the issue with the skip update occurring in the next upgrade so um so reverting on the produ on the production we suggest you to click on the revert to default button instead of doing via update sets that way on the next upgrade we always replace that customization so instead of I think the way currently people are doing it is okay rever on the dev that will capture on the update set and that will carry forward to the production um on the production it will treat as a customization because it's came via update set instead of that on the production if you revert click on that revert to base button we will uh treat the uh on the next upgrade we will treat that file as a automatically going to R to the version um so that's one option if that I know some customers that might be like too much if they had to R 20 30 files there is another option after copying the update sets they can go to the CIS update XML and there is a replace on upgrade flag uh where you can set it to true so on the next upgrade if we are shipping a change we automatically going to load that new change for you if we don't ship not going to touch but if we are shipping a change we going to load the change on the next upgrade two options either you do the hitting the reward to default button on the production or go to the C update XML Mark the customization which you want us to replace next upgrade by selecting those customization marking the field replace and upgrade equal to true so I we've got thank you p we've got another question from Lis um I this is so worthy so I think I might might have to ask L to come off me to talk um I'm going allow you to talk now so you can ask a question hi hi again thank you I remember one question that as you talk about the store applications we found that some of the after the upgrade some of the store applications well I believe all of the store applications were kept on the same version and the there were some bugs that were that were that appeared after the upgrade that we needed to upgrade the store application to the current versions to be solved and shouldn't the star applications be upgraded to the with the family release because the the process of upgrading Store applications is becoming very very combersome so for example I I do example if if I have for example for mobile we have four applications already for sever operations workspace we have for each each module itm uh well we have many Store applications and I I was thinking that after the store the family release the store applications that were installed should be upgraded to the most current version what do you think about that um so I I understand I think uh um I know your pain I think we take it to the certain version but you might have to upgrade to the different versions and that results for you to do lot of you know back and forth work and doing some manual job and all those things so we heard it and we are actually as I mentioned uh uh upgrade plans were meant for that you can uh we are currently but we included the upgrade plans two things one is like a customizations plus these application versions so customization were when we include the customization that's the where we got little push back because of people lot of customer bases on the update sets and they're never used to um they're never used to the app repo world so that's where a lot of problems are coming but we are actually in um future reles what we are planning to do is uh customizations we want to make it optional so you can actually use the uh the up plan as a deployment plan so where you can able to use for taking the application to the certain versions automatically a during the upgrade and that going to help you to uh automate all the process you are doing right now with the applications that's like a future we're trying to solve um for the currently uh honestly um I don't have any solution how can you achieve that but I understand your paino uh because it has to that's how the service no processing like it take you to the minimum version but you might have a u other versions available on the store which is not part of the Washington or part of the release you are updating okay yes and okay we are considering this for the future release we might able we might able to help you but I mean that was the intention of the upgrade plan to solve that problem but I think we combined customizations which was the little push back you can yeah maybe I give an announcement request maybe you have could have a a button or a module that upgraded all the applications to the all to the most current version that would be a nice feature all might be problem also right some customers might want some customers might not want all they want select yeah in there so in that redesign of the upgrade experience that that I was talking about being on the horizon we've heard from many customers who have that same paino that you described well we're currently beginning to user test right now and would love anyone on the call to message me as well over email if you're interested in being part of those user testings is the idea of a button that would bring everything bulk upgraded uh to the newest release but then prior to that button going through it'll basically allow you to opt out of the ones uh which you don't want to be Auto upgraded because we realize that many of our customers don't want everything Auto upgraded to the news release they want certain things uh but they want those certain things done in bulk so basically a drop down menu that allows you to click which ones should and shouldn't be so um thank you Lou um I guess that's okay thank you um I think we have one other question from Dian that's interesting so wish list items allow a customer to ZB boot an application so basically you're saying I've got the application out there as I'm installed it something whatever some changes have happened to it and I I kind of want to start over not on the whole instance of course but just that application is um that is interesting I don't think we have that uh that right right now like Z booting the application so and so what I'll suggest is to put in an an what it called put it in the idea portal announcement request then we can look into this yeah sounds interesting it sounds sort of maybe similar to uh the repair feature on plugins um but yeah I think I could I can I could relate to something like that there have been times where I kind of wish I could just kind of reset the entire application um and then you know start over in a certain in certain situation so that's inter see oh John we got Daniel in the in the audience oh hey yeah great oh so we have someone doing upgrade for the first time do you want to come off me just to so we can hear your experience or what you hope to achieve and know yeah if you you are Anonymous so we don't know your name so if you can just raise your hand in the oh yeah Nick all right so you can talk now hi Nick um your experience maybe yeah we can hear you now uh yeah I am Nick I I came from a Manufacturing Company um I just wanted to say thank you very much for the for actually for this having this kind of session because actually um yes it's my first time in to end because from my previous organization we only have a part I only have a part where in the for um only um actually only like the documentation testing part but this is kind of different so all of the questions that I posted I was one of the anonymous in terms of updates but yeah so I'm very uh I'm so Kos and thankful for this kind of session so more I'm looking forward for more so thank you good good we're glad this kind of session is opening new and Veterans here yeah definitely because some of um yes some of the um that we have shared some experiences from our um uh developers but there are also some questions that they we encountered along the way given that they're already a veterans but yeah oh this is something that we encounter on um different upgrades uh upgrade uh case toase basis so some of them are U very helpful so yeah I will'll um put that uh practice um through every upgrade that uh we do improve so yeah anyway thank you thank you thank you for the chance for this sounds good thank you Nick so now we'll review the poll results from the two questions that we asked during this session the first question was on which upgrades do you perform full testing and change management it's good to see that 78% of the attendees do uh full testing and change management for their major releases an additional 7% also do this for a paches and it looks like 15% or so just kind of play fast and loose so good luck with that the next question was how comfortable are you with postupgrade skipped record handling 28% are confident an additional 15% consider themselves expert level and 44% can feel that they know the basics 133% of you never touch the stuff so thank you for these poll results it will give us a good information on what we can cover in future enablement sessions and we look forward to seeing you at the next platform platform fundamentals Academy thank you [Music]