This is with continuation to the previous lecture of deployment of my data using chain sets and other
requirements to migrate the following competence that is at best feel and a validation from their sandbox
to use sandbox.
So the fourth organization is death and the decimation organization is QE and the various steps for
deployment to create are built in certain death.
We are done adding all the components to be migrated.
We are done under that uploading that takes it to QE.
We are done with that step.
So the last three steps up ending accessing the email chains that incubate validate the change that
incubate and finally deploy the chains that Intuit.
So no let's go ahead and do the remaining steps to complete the deployment.
First let's log into the def sandbox and let's take a quick look at the change that that will uploading.
So Florida checking the chains that will upload it.
We got to go to deploy I'll won't change it
click on continue and this will basically list on all the album and change it from dev environment and
the one that we created is a desperate so click on Sprint.
Once you click on desperate you can basically see all the details with respect to the chain that the
name description and who created it and everything and in the previous lecture itself like we uploaded
the change it.
So once you upload the change that what happens is the chain set is closed.
The status of the chains that don't closed.
So what does it mean.
It means that after that after you upload a particular chain set you will not be able to add any more
companies to the chains it meaning you not be able to make any modifications to the chains that as you
can see here that is new.
No new button available with you.
But before uploading it you will have an option of adding competence.
Right.
So once you click on I know you can add the confidence with Chase it like the ones you applaud the chains
that do any on off the other connected organization.
The status becomes closed.
And then on you'll not be able to add any more competence.
And once it is uploaded it also gives the upload history like you just uploaded and which date to which
target organization.
So this is dead and logged uploaded organization is Cuba and uploaded to be which person.
What is the status.
It is no upload.
Perfect.
We are now done with Dev enlightenment.
No let's log into Cuba and access the bone change it.
I have no logged into the Cuba sandbox as you can see here it says a gooey sandbox and an only in a
sandbox.
This being other target organization we got to access the chain side from in both chain set so setup
click on reply.
You have an option.
Click on chain set.
Continue and here you can see some description of old email chains that what in mountains it is all
about.
Please do read the description and we need to have two sections change it awaiting deployment as the
name says.
These are all the chain sets.
These are all the inbound chain sets that are available in Kuwait from different to other connected
organizations but deep since it are still not deployed in Kuwait they are just laying there and yet
to be deployed do remember only after you deploy chains that all the competencies that are available
as part of the chains it will be available in that particular order.
So no back the to the to competence that is at SFE and that this validation tool.
They are just uploaded to Kuwait.
They are not deployed to Kuwait.
So if you just go to the icons object and check for the DSP that particular field will not be available.
So after uploading you gotta deploy for the changes to take effect and deploy changes means like these
are the bone chains that are deployed to Kuwait and the changes that we created.
There was a desperate deletion 1.0 it was just uploaded to Kuwait and not deployed so it is still under
changes awaiting deployment.
So as you can see here the old bone chain said that you created and applauded from Def to QB you can
access it under in MO change that in Kuwait click on to change that name to see the details here you
can see all the details of the change that he tells you like or the name description expiration date
and sales organization basically from the organization that invoke change that has come because when
there is an inborn change that in a particular organization it can be from production or it can be from
any connected organization.
All right so this wolf organization here in other scenario is a death.
And it also gives the details of all the companies that are part of that chain set.
So far those involved chain said basically you have got three options out here.
Validate the like and delete so delete as the name say if you do just delete the change it say for whatever
reason you upload it to the front.
Jane said are you uploaded some competence which I must do Audio Blood or some incorrect competence
or whatever.
You can just go ahead and delete the chainsaw so they won't change that has gone and definitely cannot
be used for deployment.
The other two options what we see here they are important that is validate and deploy for any mode change
that floods to be got to click on validate and we got to validate the chain set.
What does this validate means validate or basically validate all the complements that that part of the
chain saw it and then check for any errors.
So let me click on validate and the system gives us four options default run local test run all test
run specify this all of these options out here are with respect to running test in the target organization.
So then you run test the system ensures if the overall code coverage is minimum 75 percent and all the
test classes on the desk methods are updated with the updated configuration changes and they pass the
test but if you're setting the default option as the name says no test will be executed and if you select
the second option that is run local test on the Destiny it organizations will be run except that which
is orginally from the install the manager's package.
And the third option that is at an all test that include the decedent from the managed packages aspect
and run specify this if you are very specific about some particular test that has to be run and then
you can go for default option in the sandbox environments.
If you go to the first option that is default no test will be executed but in the production environment
if you choose default and if you're changed it has got some Apex classes or triggers those you choose
a default by default automatically all the tests will be executed.
But in sandbox environment you respect to a of the change that has scarred Apex classes Sorry girls
are not still like if you choose default no test will be executed but it does not in production introduction
if you choose default and if you change it has got some Apex classes are triggers and then all the tests
will be executed.
However it is always recommended that you run local test even in their sandbox environments but now
let me go with a default option if we click on validate OK
effectively it says the deployments doctor and Frank the progress of the deployment and deployment status.
So here comes the fourth option.
So go for the deployment status option go.
Go for deployment status and then you can see all the change that.
Which basically failed in the validation process.
And these basically succeeded and then validation and deployment process and other elbow and changed
it from death.
And they won't change that that basically guarded in two way.
It is an idea desperate and we can see the status that is at deployment history.
The validation succeeded.
And it is deployed.
Which person.
Perfect.
So now like we are done with a step of validation.
So once validation is done the next step is to apply the changes to Cubic even at this point of time.
The changes will not be presented to environment.
Only after you deploy the changes then you can access the competence in that new environment.
So like we go ahead and click on deploy.
Let me go with the default option deployed okay.
And again let's track the progress in their deployment status page.
Go to deployment status and that it saves the desperate is succeeded.
The deployment has succeeded so now the process comes to an end.
The deployment is finally succeeded so the deployment of the confidence from left to Kuwait.
Basically the custom field and validation rules are now finally deployed to Pew Environment and in the
icons object.
We can be able to access the custom field that does the SFE and the contacts object we can access the
validation to access validation to.
So here of a process of deployment using chains it's complaining we validated the change that in Kuwait.
Yes and finally we deployed to change it in Kuwait and also do mode one point that we can use change
it only for creating new competence are for a bit existing competence in the target organization.
We basically cannot use change for deleting confidence in the system and change its cannot be used to
renaming competence s.