Now that we have a good idea about the different automation tools and sales force we should also more
then to use which to basically minimally consider any business scenario.
There may be a few different ways of doing it.
In fact like any of the business scenario we can very much do it with an apex right.
But you know should we go for Apex in all scenarios.
Absolutely not similarly a lightning floor builder.
He does a very powerful tool and can handle most of the requirements.
But should we go for a lightning floor builder for all the requirements.
Absolutely not.
So we should know when to use which tool the basic rule is that the simplest way is the most efficient
way.
So the more simpler the solution is the more efficient it this
among these are different automation tools whenever we get the business scenario we should analyze and
find out what is the most simple and efficient way of solving that business case.
We have all these different automation tools so whenever we get any business use case we should see
what all the tasks that we need to do and that.
And based on that we should select which is the most appropriate automation tool
say for example.
The requirement demands creating that a class so if they want to create a class we can go for approval
process but approval process can only create fast track clerks but not other objects and an approval
process also does not directly Asian affect guards it is basically one of the actions that we define
the apple elections or the rejection actions.
So only when a record gets to that level and it gets approved object or only that face that a court
can be created and that only task that it guards workflow is also can create records but again only
ask clerks we can define that as one of these actions however Lightning Process builder we know that
is a much better wash and off a workflow rules it can create a class it can create child A
and then it guards off any object similarly lightning flow builder aspect it can very efficiently create
direct guards.
So for creating a class if it is a part of the business scenario then these are all the various considerations
that we need to have next as a better class we can use approval process for updating in a class but
again that does one off the approval of addiction actions.
It does not direct up later at.
And even in a bad record we cannot build that existing at a that regard the process or expanding backlog.
And even in the case of a pattern of backlog the bad and should be a master detailed parent.
The relationship should be master detail.
If the bad and then the child are related to a lack of relationship then we cannot isolated using an
app like process.
The same rule applies for workflow rules as well.
Well photos get only a bit.
The record on its master detailed pattern and not its look up variant but lightning process building
on floor builder can update any a card and it's any I'll fix it later.
I got beat fan and a monster detail betting on a look up batting order any of child credit card.
So basically both these process that I am but can a bit any related record.
And that is why you always say that the process that I'm flawed literal most efficient automation tools
and sales force sending email alerts.
Hey not pretty straightforward all these four tools scandal that sending out one message we can do within
an approval process that a workflow tool segment for rapidly so we can submit our cards for approval
through approval process.
We can also use a process builder and we can also make records rapidly and we can also use flawed builder
and autos I've made Clerks for Apple
and post to check our quick actions calling Apex all these began only with the help of process builder
in Florida and not with the other automation tools required deletion.
So a record deletion lightning floor buildup is the only declarative salesforce automation tool that
we have that allows at a card deletion.
In fact we can do that for deletion to Apex as well.
Very much yes but among the declarative tools that we have in Salesforce lightning flow build it is
only a declarative tool that allows Harakat deletion
and when we consider giving a solution to the users which it was giving a visual experience or creating
a Vizard vision like we get to use it in and then we give them a business solution for all these we
can only use lightning globally that lightning flow build up is the only tool in sales force that we
can create to map with the visual experience meaning the declarative tool again because we can very
much create that same visual experience using we should force but that is coding but among the declarative
tools and sense for the lightning flow build of is the only tool that we can create an app creative
wizard which gives a visual experience to the user and also get to use it inputs
so what in the previous lines of the understood about that the different declarative automation tool
is in Salesforce.
So what then is the right time to use apex and we should focus.
So then that is a business scenario which cannot be solved by any of these declarative tools.
Then we go for a fix and we should force say for example the business scenario is very complex or that
maybe we are talking about some unrelated objects or maybe there is a very custom user interface in
one so in those scenarios that we are working with custom and complex solutions.
Then we go for a fix and we should force and as I mentioned initially the most simplest solution is
the most effective solution.
So whenever we get any business use GIS whenever we are looking for a business solution we should always
look for the simplest way of solving it.
So that would be the most efficient to.
Now that we know what all the different tools and in what combinations that can work and how do we choose
the right automation do it now like any business scenario comes in.
We would be able to better analyze which is that I do and what does the right way to form a business
solution.