As Bibles there's at least management.
The next topic that we are going to discuss about is how do we deploy metadata.
First of all let's understand the concept of metadata.
What does metadata very precise.
It does data about data.
Basically it defines a rich set of confidence that includes all aspects of the full stock on functionality
be to the user interface be the workflows be the validation tools be the apex glass beads the triggers
be the machine fills pages and everything.
That's part of the whole dot com functionality everything comes out of the metadata.
And he and I believe we understand the difference between metadata and data set for example accounts
outcomes as the object.
He just got dumped and feels it has gone to a couple of validation tools.
It has got a couple of well plurals in that and there are some 5 3 goals in account.
All right so all these forms metadata of accounts object.
All right.
And regarding to data say for example there are some 10000 account records in the system.
So those 10000 account records they fall into the category of data.
So maybe it's something that stores data.
So this is the difference between metadata and data.
Say for example you look at the application that you are working on.
Let's consider some sort of sandbox environment and protection environment as we know there can be only
one protection environment.
That's a real time environment and sandbox environments like a can be many.
Depending on the business depending on the requirements.
How many sandbox environments they have gone for good has many sandbox environments you actually have
in the system for our example let's consider that a three sandbox environments.
The def sandbox Cuba's sandbox and the staging sandbox and production you know that is only one production
environment.
So whenever we want to make some configuration changes to the system every project has guard their own
deployment process because if a sandbox that exists it exists for a particular reason.
Say for example the def sandbox it is purely for development q a sandbox for doing on the Q activities
the staging sandbox kind of a preproduction there can be other sandboxes as well say for example purely
for the purpose of integration testing or for doing some people is easy there can be multiple reasons
for a sandbox to exist in the system.
So as an admin as a developer as a sales go uncertain that you work in a system look in a project you
got to understand what all the different sandbox environments that is being used and what is the purpose
of those environments and considering a deployment.
Why does a process that they follow for following the deployment say in some project it might be like
every change that goes from Def and then Q way and then staging and then they migrate to production
and in some projects it is like a no Q way sandboxes broadly for some other integration so you don't
really like they do not bother about the cute sandbox to the deployment process is like a death and
then staging and then to production.
So you're just talking up to the business totally up to the project.
The deployment process that they follow to deploy changes to production.