[Music] in order to subscribe to my channel please click here or click here please share comment and like my videos and channel hey guys this is Gaurav welcome to SAS word service now this session is about service now update sets as a developer or administrator you must have done lot of configurations or developments and service now now in order to move those changes into different instances you need update sets so let's start with the definition of update set so what is an update set an update set is a group of configuration changes that can be moved from one instance to another this feature allows administrators to group a series of changes into a named set and then move them as a unit to other systems for testing or deployment if I give you a quick example that you want to perform some changes on the form you add two fields on that form that means you have changed the layout of that form at the same time you have also added a UI action a button on the form as well now how exactly you can move these changes to the different instances so in that case you can capture these changes which you have done in just one unit and then you can move them into a different instance now this particular unit which will have a name is an update set update sets movement let's say you have instance one so this is your maybe development instance and then you have instance two this is your production instance now you have to move some changes that means you have done some changes in this particular instance so you have changed one change to change three change four like I said forms layout changes you have added a button you have created a client script you have added a business rule for different changes but you have changed those configuration development in instance one now how this will be moved so basically you will capture all these changes and these changes will be moved to another instance with the help of updates set that means same change but you have an instance one will be replicated in instance two as well update sets application in order to perform all these update sets capturing a movement ServiceNow has a separate application that is system update sets which has different modules to manage these update sets let's take a look in my personal developer instance in order to go to the application you need to type system update when you will type system update you will see this application with some modules if I click on the first update sources so this is the first module where you have to configure all your remote instances configurations because you can only move the update sets the changes you will capture with the help of update sets but those configuration has to be there so that it can know from where I have to pull the data I have to pull the update sets changes in this instance then we have retrieved update sets so basically this is like a primary instance or maybe a destination instance you can say now this is like a production instance and you are pulling some data from your dev or UAT instance in that case whatever changes you are pulling from your lower instances you can see here then we have update log so whatever data whatever changes you retrieve all all actions are being logged and you can see here then you have local updates sets so similarly in production as well even you are pulling some data you are pulling some customizations from another instance those are also being stay stayed here as a local update sets that means those are the update sets for this particular instance so whatever changes we have inform of update sets that you will find here then we have merged update sets so you can also merge if you have different update sets and you want to merge them into one you can also do that ServiceNow provides you that feature as well then you have merged completed update sets this already gives you functionality that the update sets which are already completed you want to merge them you can just merge here and then you have update sets to commit that means any update said you have to commit that means you have to install in your this instance that you can see from this particular module when to use update sets now this question is really important to know but I will just explain you a little bit about update set that whatever changes which are like development changes or configuration changes all should be captured as a development they always gets captured in an update set even you don't create anyone any any single update set and that update set is basically default update set so ServiceNow automatically from the beginning keep one update set even as in a fresh instance I will quickly show you one instance which I just recently enabled this one and if I will go to a I'd set and I will click on local update sets here you will only see one update set that is default that means whatever changes you will be doing even directly on insistence that will be captured in this particular default update set now why ServiceNow does that because just to make sure that you don't miss or or lose any kind of development or changes you do in this instance and that's the reason ServiceNow automatically keep one update set that is a default updates always in progress the question here is when to use update sets so you should use update sets when the changes you want to keep in every instance so maybe you have different instances in your organization and you want to keep those changes in every instance and you don't have to change it manually so just an example you're writing a business rule in one instance now you don't want to write a business rule again in production so in order to make sure that all the business rules are being written in every instance for the same functionality and you have to move it to every instance so then you need to use update sets you have to use update sets when all the changes with can change the baseline and can give impact so any change you want it can it can give impact it has to be done directly with the update sets it should not be done directly in production the reason I mentioned here that why we need update sets because you should not do these changes directly in production and that's the reason we have these update sets so that you can do those changes in lower environment which is kind of a replica of production and then you can move it to the different instances even in production and after testing as well and that's the third point a changes needs to be tested in lower instance before moving to production now any kind of change maybe you are creating a business rule you can't directly create in production because you know no that particular business rule will give any impact so it's really better I think it's mandatory I would say that you perform that development into lower instances moving to different instances tested thoroughly and then move it to production items captured in update sets so there are a lot of different items and service now which are basically captured automatically so you don't have to do anything manually to and force them to be captured in update sets so items like form configurations so whatever configuration on you do on form it does capture in update sets related list configuration business rules transcripts UI policy UI actions notifications script includes UI pages and more basically you can also change these these items in production and that will also be captured and default update set however as I mentioned you shouldn't do that so you have to create an update set indoor environment capture these changes which I am showing you on the on the screen and then move them but as I mentioned items captured in update set that means you don't have to do anything any extra activity you just go into your lower instances create update set name it properly and then make it current which we will see a little bit later and once it is done you just perform the changes create a business rule create a script include all those changes will be captured in that particular unit new unit which you just created now items not captured in update set so that means there are some items as well in ServiceNow which you cannot be kept capture which cannot be captured in update sets and those are task records like you have records like incident change problem these records whatever changes you do in these records they don't change they don't capture in update sets then we have users we have user data you do some change in the users racket those doesn't change or does sorry those doesn't capture an update set groups any rackets you have in groups table those doesn't capture in update sets then you have scheduled jobs scheduled jobs as well even scheduled jobs are part of kind of development but this they are still not captured but you can still do force capturing but that's kind of a additional feature in ServiceNow that anything which is not captured and you want to make it capture able in that case you can directly push it into an update set as well CMDB rackets so all the CMDB repository we have it cannot be captured in update set system properties and last I think it's just more so extract rather a lot of other things which we talked that the other things can be captured a lot of things cannot be captured in update sets update sets planning process now before you before you start moving the update sets you have to make sure for some of the points but means you have to plan your moving of the updates as properly so that you don't get any kind of issues starting with same version instance that means when you are promoting the update sets from instance one to instance two and since one and instance two should be on the same ServiceNow version like Madrid Orlando New York both the instances cannot be different because the reason behind it if you are performing a development and lower instance maybe in Madrid version and you are moving those changes into Orlando thanks might break so it's really it's kind of a mandatory I would say from ServiceNow that both the instances should be on the same version when you have correct update set is selected as a developer or administrator when you perform development or do any kind of changes which is being captured in update sets you have to make sure that right update set is selected on on your on your development screen or in your service now in the same session you are working on second thing is instance is third thing is instance is cloned now you don't want that both the instances are undifferenced aasaiya tees are different or some data is changed no or different in that case the best way is you have to copy production to lower instance and that's called cloning so you have to make sure that whenever you do any kind of releases or maybe major releases your instances are keep on cloned then we have identify path for update set movement now this is also important point in in the planning process of update sets because when you have different instances in your organization you might have dev you might have IT you have you etui you might have staging you might have production or maybe some temp instances or other instances as well but you have to define a model a path at how your update sets will be moved that means from instance one to instance two then since three and then at last add-ins in instance forward the next point we have is planned went to commit update sets in production now this is also really important because production changes can also will also give you any kind of impact or or user may be get surprised why that new option got gotta go got added so in that case you have to make sure that you are planning your movement of update sets in production properly then we have clear naming convention that means whatever name you are providing to your update sets while creating a new update set it should be pretty much understandable if you're working and it releases some sprints in your development lifecycle for any mod module in that case you can define some standard naming convention for your organization so that everybody every developer can understand that naming convention preview and comment while you move the changes you move the update set into different instances you have to make sure that you are properly previewing them so that you can see what all errors or any kind of warnings are there you you fix those warnings and errors and then after review that means you are reviewing it before moving as well so when you are ready that yes I'm ready to move this update set you have to make sure that all the customizations which you have done has been captured not off time is it has been seen the developers sometimes forget to select the current update set the update set which they want to current development to be captured so you have to make sure that you are reviewing your update set you have proper customizations all the expected customizations and then only you are moving to the different instance update set promotion now how exactly update sets are being promoted in different instances so we will start with dev instance so you perform the development in dev instance any one of your dev instance and then you have u8e instance then you have a staging instance and then you have production so dev is for development you is for user acceptance testing staging is like a pre prod instance and then you have production instance main instance where all your business users live users are working now you perform the development you capture the update sets in dev instance and then you move that update set in to you ET instance now this was the identification of the path so that you can perform the developmental production that means move the changes till production then you perform the UAT you perform the testing all your end-users perform the testing once everything is succeeded you move those changes to next instance that is a staging now in staging you still do a one round of testing again that if everything is good once those changes are being moved into staging now you have a last stage that is production implementation that means whenever you have planned for your production release if that date has come then you will move all the changes from staging instance to production instance system updates set tables we also have two different tables for update sets one is update set the update racket which you create it's a different table and that stable is sis underscore update underscore set and that's update set table where you add different customizations now all those customizations basically which are captured maybe it's a form layout related list layout related list configuration adding a business rule all those basically all data is an XML format so those are called customer update so for each entry for each dictionary entry you have it creates it creates a customer update and then add into your update set so basically customer update is a related list of updates set so when you will open any update set you will see the related risk customer update and you will see all the changes you have done for any functionality you have changed prepare instances for update sets promotion let me start demo a practical demo so that you can understand the whole update sets process but how exactly it works so I will go to my personal developer instance as I said I have two instances one is this one that is dev six three zero zero eight and then I have another one which is dev seven nine one one nine let's keep this one as development instance and this one because we just got recently so let's keep it as production because I have not done any kind of changes over here so in that case what we will do we will go to our this instance but this is development do we need data here do we need to pull the data here no because you are going to do development here and then you have to pull these developments in your destination instance this is this one that is prod so I'm treating this six three zero zero eight as production instance and another one as development instance just an example to show you this demo now what kind of preparation you have to do so if you remember we talked about update sources so first thing you have to do is you have to get the connection enable the connection for your development instance in your production instance how we will do that so we will click on create new I will give it a name I will just give a name maybe maybe I will just copy right from here so that I know I have this one here I can see I can select what kind of instances is it is development production test so I will keep it development here I have to give URL but that's how it will be able to connect so I will give you RL I will just lock this here I will give you user name and password so user name is Edmund I have my own password which I will type it here I don't need to give any kind of short description and I can keep this active and in order to test the connection I have to make sure that my this instance is able to connect to my another instance like this instance so in that case I will click on test connection when I do that it says connection is ok however parent instance I think there was a really different error you saw I think maybe let's let's because there was that error that message was related to I think versions so let me check the versions first but before that I will just quickly submit this connection so connection is successfully so let's try again maybe we can see that error version like New York and does not match your local and Madrid okay so in that case your another instance that means this instance is in Madrid and this instance is in New York so they can still communicate they can still share the update sets you can still move the update sets so as of now I don't have much time to get a new instance so I will continue my demo so that you understand but you have to make sure that you are not moving the update sets in different versions when you are working practically in your organization or in your business service now so what I will do I will save this racket once I will save this racket it will create this particular racket here and if I click here again you will see but it is still showing you when one message that yes everything is good but it seems like both the instances are on different versions so as of now as I mentioned it's okay for now so that was the first step as a preparation next is enable update set picker now where exactly we will do it we will do it in our development instance because we don't have to do it in in our production instance it has to be done in development and so I will go to my development instance which is right here you have to click on this button settings this bar here button you have to go here developer now here you will see show updates set picker in header so I will enable this this is enabled and you will also see this here so I will close this you will see update set picker has been US enabled now you can see all these current update sets I have in my instance and if you will click this button you can also see the which current update set is there so as of now default is selected that's how you can enable update set picker so even if you are doing any kind of development and you have to you have to change your development maybe you're working on different functionalities and you have to change your update sets quickly because you are working on different developments so what you can do you can directly select any different updates as right from here and you will also get the message your current update set has been changed to SAS portal so the important point here is it is all totally depend on the session when you login to the instance whatever update set is selected at the top that something will be captured that means any development you would do even maybe before before that you have some different different updates set selected but now it got changed maybe later on or somebody else changed maybe I'd leave somebody else would not log in but maybe you forgot it and you are doing those changes for any other functionality which is not part of this update set so even the development which you will do right from like from from now onwards it will be captured in current update set which is selected at the top so you have to make sure which is one of the point which we which will learn that you have to make sure that you are you have selected the right update set in order to perform the development and capture the update sets for your functionality create an update set and capture development changes so let's create a new update set and capture different development changes we will try to create a new functionality maybe so I will go to my personal developer instance this is my development instance so I will go to local update set in order to create a new update set you have to go to local update sets then click on new button here here the previous update sets which maybe you were working on some update sets it will automatically add second version but I can just remove it delete it and I can just put update set underscore demo I am just selecting this naming convention just to show you the demo but in your organization you can definitely as a developer or as a lead or as an architect you can put some kind of naming convention so that every developer in your organization is following the same naming convention so I am I can put up date set demo here you can see state here it says in progress complete and ignore now in progress is basically its self understanding that you it's for current development which you are doing so that means if you want to capture the development then you have to keep it in progress but if you will save it will it capture the current development which you will do so the answer is no so but in order to do that you have to click this another button that is submit and make is current so I will click on this submit make this current you can see you will see a message at the top your current updates I haven't changed now and you will see changed update set right here in the update set picker so whatever changes you will do now will be captured in this update set now what I will do I will go to incident or maybe problem so I'm going to problem rackets here and maybe I will just add a business rule show maybe info message or let's let's create a client skipper maybe I will just create a client scrip I'm going to climb script here I will do show alert and here I will do you I type Dexter for now type it's on load application is global and here I can just do alert this is a demo for update set so I have added this script here and I will just save it when you will save it it will automatically capture the first version now that is the versioning we have in ServiceNow which basically gets captured in update set and if you will see at the bottom its versions here its XML which the update which you have changed and then you have this update set name you can see it is our current update set which we selected which we just created that is update set demo and I can click this and you will also see the changes so this is how it looks like now this is something system update version it's it's another table of update set we talked about two main tables but this is also another update set table that is this update version table now this is the whole XML record for for the new racket which you created XML you can see all the data you you just mentioned even the script you can see here so this is how you you capture the changes in update set it show you the versions as well so I will show you quickly one thing about versioning as well so if you maybe add a comment as I change something and I will save it now this will again captured in the same update set but with a new version so you can see now I have a new version that is also current these are two different development we have captured and one we have comment and another we don't have comment now how can you see these changes so there is a really great functionality that you have to check these boxes check any two custom changes or versions you have select here and you have you have this option called compare when you will click this now this will be really important for a developer to understand what exactly has been changed now what you can do you can just go and check which area which particular thing has changed in a whole line script now this this thing in blue in color will tell you what exactly has changed so it is telling a script part has changed and now you can also choose say see the deviation so you added the comment in the current version but here we don't have anything that's how you can compare two versions now you can just go back or maybe if you want to revert to the selected version you can do that as well or you can also merge both versions it's totally up to you but I will go back so you have captured this promote update set to next instance so now the important point is you have your done with the development but now you have to move this update set to another instance that means same change same alert into a different instance that is the prod instance we have so let's go here what exactly you have to do you have to go to the same update set so for that I will click here as of now this is in progress so you have to remember one thing if your update set is in progress then you cannot move to a different instance so you what do you have to do you have to make it complete because another instance your prod instance will only come to know for all the changes which he can capture maybe pull the update sets which are incomplete status the other option we also have ignore at some time that you have some some you have done some development but now you don't want to move to another instance you can make it ignore so another instance your prod instance will not be able to know or will not be able to pull that update set as well so as of now I am making it complete and I am saving this once this is saved you will also see the message this update sets was closed by you that means you are done you are done with the development now if this particular changes are ready to go to different instances so we will go to our Pradhan since now here now what what's the next step here we will click on retrieve completed update sets so I will click here once you will click on retrieve update sets it will hit your load environment that is your development instance and check what all update sets I can pull but you will also see one thing that you also had some other update sets you must have seen that I had different other update sets as well that will also be pulled into this instance because those are also completed so in that case I will close this but you can see it says three update sets retrieved and previewed that's a functionality we have I think ServiceNow came up in London version that they now they are already previewing it now what exactly this preview is so I will show it to you I will close this and now you can see here so whatever data we pulled we retrieved you will see in this particular related list here you have these three update sets and the one which we also created recently the new update set to capture that alert development we did it's also says state as previewed but but if you you can also disable this particular functionality that means it will not be previewed and what exactly this preview is preview is basically it checks all the conflicts any kind of dictionary entries are already there or same client script it might happen same client script is already available so those other checks it does before committing anything because the next step is committing so this is our production as I mentioned we have already retrieved it and you can just click on run preview again it will show you what exactly it does so I will click on run preview now in this particular process this will also check any kind of error warnings and if it not then it will show you right here if it has any kind of issues it will also show you if anything is inserted updated deleted or if there are any collisions that you will see here as of now this is not committed that means this particular alert is not even available right now because we have just previewed it so what we will do in order to explain you better I will just open problem form so that you understand so I will just open any single problem maybe this one so if you remember we wrote that client stepped on onload so as of now you can see I am loading this problem form but I'm not getting any kind of alert right now because that development change is not here yet because we have not committed our update sets now I will go here and this time I will click on commit because I have just checked all the errors I'm ready to commit now how click on comment when I click on comment it will again give me a pop up and run the commit you can see it says committed in zero seconds succeeded no errors nothing you will close this now this is the final stage if you have committed the update sets that means you are done that changes will be reflected in the same instance you have right now so I will go here and this time I will reload the form I'm reloading it this is a demo for update set we wrote that client script in that instance in development instance we didn't even change anything in this instance but we just moved the changes into this instance and then same same changes are being replicated on this particular instance but that's how you start the whole process of development and capture in the update sets promote into a different instances the next topic we have is backup off update sets it might happen many times that you are performing development in your development instance however you also need to clone that instance from production and if you will clone it whatever ongoing changes you have will we will be gone so that's the reason what developer do the developers they take backup of those update sets and how exactly we do that I will show you quickly so in that case I will just click on close and I will go to my development instance what I will do I will go to that climb script again and I will make some changes but before that let me just capture the update set so I will because you can't select that update set anymore because that's already closed so now I will go to local update set create a new it says update set demo - I am ok for now I will click on submit and make current because I have reduced those changes I will go again on problem open and I will go to client scripts I will open my same client script now I will do some changes because I have moved my changes to that instance for first one here I will do alert maybe I will change the message this is a changed demo message now you're doing this development suddenly you're you got to know that you have to clone the instances so what you will do that because you are keep on developing the changes how how exactly you will make sure that I can also move these changes in more in in my next instance so what you will do you will go to your current development so whatever development you have done and you can see the changes right here you have captured the changes and target DM is show alert the client script you can just complete it once you will complete it you know that it is still ready to be pulled from that instance but as of now you can't do that because you have to first clone it then only you can you can just move the changes so in that case because you might need to add so maybe some more changes into this particular client script so in that case here is an option that's called export to XML you have to take the backup of this update set so I will click here I will do export to XML here you can see it has been exported it is in my system now I have taken that backup so maybe now you you got the cloning and cloning is done so in that case you will not find this update set anymore but now you have to import it back to your instance how you do that so as of now I'm not importing back to my development instance I will import it directly into prod instance just to show you the demo how you import back to the instance so in that case you go to your development production instance but just let's let's say example this is your development instance again same instance from where you took the backup so I will go to update set here you have to go to retrieved update sets then you will go to retrieve update sets at the bottom you will see a related link that is import update set from XML so you will click here it will ask you to upload a file xml file so you will upload it now this is the one which i just downloaded so i will select this one select it now i will click on upload then you will upload it the first step the first state would be loaded because it can't be committed so even in even in that situation as well when you were reviewing it when you retrieve the update sense first it gets loaded then it gets previewed and then you come at them similarly you have the same case here you have to click on preview update set to check the errors so what i will do i will click on preview update set it succeeded there is no conflict that means it can update the alert without any issue the same clients kept maybe I will close this and now I will comment it but before that I just want to make sure that you understand what exactly we did now you can see it says 0 inserted because it was not a new client script that transcript was already available in your instance and now you are just updating it and that's the reason it says updated one here deleted 0 collision 0 total one and I can click on commit when I will click on commit my same code change will be replicated here I will click on close and I will go my problem form again I will reload it and see if it is reflecting the same so I will go to my problem form and I will open any problem racket awesome it says this is a change demo message and that's what we did we just captured we just change the script took the backup imported back to my instance and you can see the same changes are replicating the next part is merge update sets now as you know you can create different update sets so ServiceNow also gives you an effect gives you a functionality where you can merge friend oblate sets maybe you have different developers developer one developer two developer three and they are working on same kind of functionality maybe they are working on incident table all three developers now it's really it's I think important that you don't give any kind of conflict between the developments so the better approach would be because you also have so many update sets because if you will have for example you have a hundred of bleed sets it will also be very difficult and lengthy to move those update sets one by one commit them preview them and then put it into different instances now the better approach is merge update sets so you Club different updates that may be ten ten update sets maybe the updates are which are kind of same functionality in that case it will save two things one is time another thing is conflict as well even I have done a change on form layout and even you have done maybe you are developed you are a different developer those changes will be captured merged together and no conflicts will be seen in any of the instance so if I take you here and I go to my developer instance and go to update set here we have merge update sets so any update set you want to merge you can select them you can say you have to click on merge you can also reset the filter if you want to merge the specific update sets that is what you can do here you can also directly click on merge completed update set so if whatever updates that you have already completed you want to merge them and move them that also you can do you can just click on merge so you will click here are you sure you want to merge it for these you can cancel if you don't want all these for I can click on reset filter or maybe we can add a filter right here here this example this one name it starts with I will run this now only these two update sets will be merged so if I click here Marge you will see it will only say two initially we were getting four so that's how you can filter out any other update sets that you don't want to merge so I can click on merge are you sure yes okay when I will do that you will see something both the update sets have been merged and here I have merged update sets but what about the one which I just created let's see you can see now both these update sets their state as an ignore that means these update sets will not be moved to different because their customer updates which we had changes we had they have already been captured and moved to this one and we only have just one clients kept so you don't have to worry about it it also says which update sets are being merged and these are the one so that's how you can also merge the update sets the last section we have is manage conflicts as you saw we were trying to preview the update sets and then we were committing them that means you have to make sure that there are no conflicts there are no collisions so what we exactly we will do we will try to create some collisions and these conflicts and we will fix those collisions so let's see how exactly you can do that so I will go to my developer instance here or maybe I think to create a conflict you have to do some changes directly in the production instance so I will go to my production instance here and then I will go to my client script now what I will do I will disable it I will disable it directly from here so I will disable it just to capture the changes this is done now this client script is disabled that means you will not get that error anymore but you are doing directly in production now maybe let's example that this is your you 'ti instance and another one is your developer instance I am just changing the scenario because you have to make sure that you don't get any conflict before you perform before you put things in production because your your UAT your staging everything is cloned and it is like a replica of production so in that case I have deactivated this client script now what I am doing I am going to my dev instance and going to same client script I'm going here I'm going to climb script but before that I also need to capture these changes so what I will do I will go to update set local update set click here new it says merge but I don't want that maybe I will just pick the one which I had like this one third so I will go here create new I will give it three now save it and I also I will also make it as a current and you can see we also have this in related link so I will click this make this my current this for current developer for this session which I have logged in right now this update set has become current so whatever developments I will do this will be captured in this one right now so I will go to my problem again problem table transcript here I will go to clients crafts and same show alert as of now you can see it is still active but in production or maybe that you are the instance which we had we just did some changes directly in that instance how we will get the conflict so in that case what I will do I will try to maybe this is to see conflict I will save this this is saved the new change is saved basically in new update set which we just had or which you just created so I will open this now this time I have this one and I will make it complete I am clicking on save and now I'm going to my another instance this one here I will retrieve new update sets and I will go here update sources and I will retrieve new committed or completed update sets in my lower instance this instance basically so I will click on retrieve completed instance correctly you've completed update sets it says one update sets retrieved two updates as would not retreat because they already exist as a remote update sets okay so we already had them so here we have updates as demo 3 now if I will open this that is what we wanted I have already created this conflict myself you can see that it says in order to commit this update set that means if you want to replicate these changes or commit this update said you have to first fix this collision anyhow you can see here nothing is inserted updated deleted the only one thing it is showing its collisions that is one and if you see what exactly which particular part is being collisions so you will see here it says error it all it will also show you what kind of error it is it is found a local update set newer than this one so is telling you that it seems like there is an update says local update said which is already newer then maybe it was updated later before it was developed before this was developed it was already updated in in this particular instance so in that case what he can do so you have to troubleshoot now you have to manage the conflict you have to fix this conflict so you will see these options like compare with local show local record show local update accept or escape now it's totally up to you so I will explain you these options as well if you will click on compare with local so it will show you that what are the differences between two updates that the one which we already have in the instance and the one which you are getting from another instance so that is what it will show and if I click this one you will see okay so this message is also changed I think something else as well this one this one is inactive here is active so I will go back so due to changes are highlighted I will come here but it says show local record show local update except remote updates skip now show local show local update it it will directly take you to the same records but the important part to take some action on this one is accept remote skip remote that means if you will click on accept remote so whatever changes you have done in your dev instance do you want to replicate it and ignoring whatever you have in current one then you will click on accept remote but if you don't want to replicate the changes which you didn't did it in Devon stance then you have to click on skip remote update set and then you can comment it so in that case I will click on accept because I want to show you that alert will show you again so you can see it says I have handled it so it says all problems have been addressed click commit a comment update set below to continue but before that I want to show you that message if I have it because as of now I have not committed by remote update set so I will go to the problem forum here I will open it you can see that alert message is not there because your client script is inactive but if I will go here and commit it now I will click on commit it say it will say succeeded I think shouldn't take much time three seconds I will close it it says deleted zero collision is I think done we are done it's committed now what I will do I will go here and I will reload it that alert should be seen here again awesome this is to see conflict so as you can see we just fixed our collisions and you took some action and it is also replicating a right in your instance so this is how you work on update sets as I mentioned you have just need to remember little precautious when you perform these developments you have to make sure that you have selected the right update sets and that's how you move and promote different update sets into different instances I hope you like my session so thanks for watching this video have a great day