So now that we have created a sandbox successfully the next step is to establish the sandbox connection.
Basically a deployment connection.
So the sandbox that we created it is very much in use.
Users are able to log into the sandbox successfully and they are able to do their development testing
and they completely they can use this sandbox.
But at one point when we need to migrate the components when we need to deploy the components from that
sandbox to a different environment bead on the sandbox not be a production environment.
The virtual environment it is then a of that is need for this deployment of meta data then we need to
have a deployment connection in place only when two args have a deployment connection in between them.
Only then we can use change sets that either UCLA or whatever competence so a deployment.
So establishing a deployment connection is essential for deploying that data competence between two
order.
So now let's understand how do we create a deployment connection between two all and a hero to all the
learning purpose we are using develop in addition and we do not have access to sandboxes so similar
to the previous assignment.
Even here I have some screenshots which we can use it for a better learning purpose.
So I log into the sandbox for which we need to establish our deployment connection log into that particular
sandbox and in this setup if you search for deployment settings you will be able to find deployment
settings and the page will appear similar to this.
So here we have deployment settings here.
And here we have enlisted the production org because because only one or other of that is available
but in real time there are more args.
The production order will be there and on top of it.
If the company has got more than one sandboxes on the sandbox as will be listed here and here it will
show us.
What does that basically connection between that particular environment idea.
That environment here we can see that that is a node deployment connection between the dev sandbox that
could be logged into and the production sandbox so right now that is a node deployment connection between
these two arcs all right between the dev sandbox and the production.
OK so now what we're going to do is we are going to establish a connection so here we have the production
arm.
Click on the production org.
This will give us other details.
However it is defined and then we have allow in bone changes and accept along changes.
So what does this inbound and outbound as the name say is inbound means incoming and outbound means
outgoing.
So only then this Marxist check that is inbound changes.
It means that it can accept changes from production org but it cannot give out its changes to production
arc.
Basically it can only accept the changes but there is no outgoing and depending upon the requirement
for depending upon how the org has to be configured it completely depends whether you have to select
both or either one of them.
In this scenario I have selected board and once you do that you can see it just to make changes from
Def can be deployed to production and changes from production can be deployed to def because we have
selected both inbound and outbound and now we have successfully established a deployment connection
between Devlin production.
Similarly you can see all the other sandboxes listed out here and you can also see how was a deployment
connection established between the def sandbox and the other sandbox.
Say for example we have a sandbox SKU way.
So here you would say def Q A.
And what does installation if there is no relation to children red.
If it does one way to chill one way and if it both ways it shows like this.
So this is how we establish a deployment connection between two environments excess force and after
this deployment connection is established we can use chains it's a full stock on my d to deploy over
meditator.