hello in today's demonstration I'm going to walk you through setting up back syncing in your X-Type CI CD pipeline now back syncing is one of the most important and critical aspects to automating your CID CD pipeline within servicenow and the reason for this is no matter of adding or layering external tooling or trying to apply traditional devops tooling is going to overcome one of the fundamental Basics to a platform-based engineering which is the platform owns the code you don't actually own the code so you're not dealing with a file based architected app and so one of the ways to help streamline things is to not only set your deployment flows going forward as you see here but also to get them go backwards so let me explain as you can see here in my environment within X-Type and again I got here by going to the CI menu item and clicking setup environment you can see I have three development instances and they are going to be pushing their updates to my uat environment in my uat environment we'll be pushing updates to production but the question is what if I make some hot fixes to uat or what happens when this developer here updates their code into uat and these developers get up the next day and start working on the same module or working on another module a set of code that actually is dependent on the module that the first developer did so one of the ways to reduce and get rid of these conflicts and these collisions is to back sync so what I'm going to do is walk you through back syncing my production environment to my uat environment and as I say a lot of times the beautiful thing about X-Type it is natively built for servicenow within servicenow so we're leveraging a lot of the good things the servicenow already has so there's only going to be two things I need to do here I'm going to set up my production environment to be a remote instance for my uat instance and then I'm going to set up a stage flow that'll automatically push any updates that make it into production automatically into my uat environment now in a typical environment what I also want to do is anytime anything gets pushed to uat or my QA environment or my QA instance I want those changes to be communicated out and pushed to all the other development instances simultaneously that way developers are always working against the latest of in everything that they're doing in their instances I don't have to wait for clones I can automatically get the latest updates that anybody in my team is making because they're automatically communicated or synced back to me as they push into uat so let's do this it's pretty pretty simple so I'm going to go ahead and move to my uat instance and set up my production instance as a remote instance we'll take note of this name for the number rather 14 22 62 easy number to remember 14 22 62. and we're going to go ahead and add that as a new remote instance in my uat environment and we're going to call this prod and here's our servicenow instance 22 62 and then password I almost forgot to finish the rest of the URL .com We'll add the precursors test the connection that's okay submit perfect now let's go to my prod instance and we'll refresh our screen it'll take it a second to recognize that it's been set up it can take a few moments there we go we can now see we have a bank sync coming back from production to uat now right now this back sync is manual but the whole benefit of doing back syncing is for it to be automated so as long as there's information that has changed we want that information to be communicated and synchronized or deployed automatically to all of our sub prod instances so this could be done by going to our deployment flows screen and again we will now go ahead and take a look at the connection that we just set up here here it is and we're going to click on this back sync flow I'm going to click Plus and we're going to click on our trigger in this case we want it to be automatically deployed as I mentioned before and I'm going to click assign and then that is that now if I had a hot fix instance somewhere out here in my ecosystem and I deploy hot fixes to production those hot fixes are now going to be automatically deployed to my uat environment as well and at this point I'll just do a rinse and repeat and we'll set up back syncing to my three Dev instances and what would happen is in the case of a production hotfix deployment that hot fixed deployment will be automatically pushed to uat and then automatically to my three Dev instances