All right.
In a previous video we understood about the various troubleshooting techniques for after work processes
when users start using approval processes.
As a senior Bragman what are all the different type of techniques that we need to follow for troubleshooting
any issue within Apple process.
Perfect.
So know as a continuation of that but in fact in a little different aspect we aren't going to understand
what all the different concentrations that we need to note while using Apple look processes are in fact
annoying this as a senior admin would greatly help us in our day to day admin job so these are some
of the considerations that we are going to discuss now.
To go with submit for approval button can be overridden.
So what does this mean in Salesforce when we create and activate an approval process for any object
and then automatically we'll have this submit for approval button in the detail page.
Right.
So if we want to submit any record for approval we use this button to actually automatically get that
record approved through the various steps.
Perfect.
We know that and submit for approval button is actually one of the many standard buttons that we have
in sales force.
In fact let's quickly go to or develop Rog.
This is the extracurricular Custom Object scroll down scroll down to the section and button links and
actions.
Here you see the various buttons links and actions available in this extracurricular object and these
buttons that are available out here.
These are these standard buttons.
The delete button edit new view.
And these are the standard buttons.
However these stand buttons can be overridden meaning these standard buttons can be overridden with
a custom visual for speech.
Say for example this new button this new button once you use that standard new button automatically
that standard a new page layout appears right.
That new page appears.
However if you overwrite it because you have a different specific custom requirements then instead of
that standard page on clicking that new button a visually first page would open in the way that you
have designed it that does what is called as overwriting a standard button.
So say for example I hit edit I'm editing this standard button and here that is an option if you want
to know what I did.
If you want to override it select the other option and choose the visual full speech I.
We have not created any visual flight pages so that option is not updating all debt.
However that we should focus pages those we should fill pages will appear here and you can choose which
page it should be used to for overwriting this new button so this is the agenda and behavior of how
to override a standard button and sales force.
However if you see here the button submit for approval void appears on the detail page it is not available
out here meaning the submit for approval button can to be overridden in case the business requirement
in such a way that you do not want to use the regulatory approval process in.
Instead you want to use a custom requirement and ask for the business in that scenario.
You can't override the star submit for approval a standard button.
But if the business is very specific about the customer requirement what you can do is you can create
a new custom button the option is out here.
You can create a new custom button you can use the vision for space and make it work accordingly.
So basically the underlying concept is that the standard submit for approval button assets can be overridden.
But if the business is very specific about a custom requirement we can create a new custom button and
we can use that instead of the seven for approval standard button and you can hide that standard as
have been for approval button from the page layout.
So though we cannot directly override the walk at all would be to create a new custom button and hide
the existing standard button.
This is all about the first consideration submit for approval button can be overridden.
Perfect.
Moving on apparel and steps can to be added to an active approval process.
All right.
So we have actually created an approval process which we activated also not what we are going to see
is whether we can add apparel and steps to an active approval process so for this Let's navigate through
the approval process that we created.
So this is about approval process.
This is activated.
And here are the steps that we have defined for this I.
There is only one step out here.
We have not created multiple steps.
That's OK but what we are trying to understand is about the new button here.
We do not see any new button here meaning we can't add a new approval steps to an existing active approval
process.
So it is our best practice to always validate the approval steps before we activate any approval process
perfect.
Moving on additional actions can be added to an active approval process.
So this is similar to the previous one.
What basically can or can't be done to add to approval process for us to be understood approval steps
can be added and no actions can be added.
You see you can still add further actions to the full blown existing active approval process.
Perfect next is additional analysts may be added to an active approval process.
All right.
This is a little tricky one of these should be able to add additional approvals blunt active approval
process.
However that is a little trick in this to understand this let's navigate to the approval process again.
We are here let's go to the apple and steps heed the edit button.
Go next specifies a step criteria.
All right.
Assigned to apple juice while configuring this apple process we automatically set this to manager.
However you can always add additional apple using this option.
So here you can choose use us.
And then you can add additional users so that they'll be able to approve.
And in this scenario if you see the on adding additional users an active appellate process.
Right.
We have that option very much available however if there are a record which are already in this particular
step of the approval process at that time and these additional approval is be able to work on that record
but otherwise I think additional capital was should work perfectly fine.
All right the next US cross object field update in re-evaluated workflow rules are ignored
let's again consider the same approval process we created for the extracurricular object let's say that
approval process specifies a field a bit action.
So basically what happens when the approval process gets triggered that field update action also gets
completed but if the field update action reliably waits the workflow rules for the updated object in
our case the extracurricular object then those re-evaluated workflow rules may or may not work depending
on a scenario.
So when then would it work and then it would not work.
It would work if it includes updates within the same object and it would not work if it includes cross
object field updates.
So that is what it means cross object field updates in a reevaluated workflow rules are ignored.
This is a very interesting concept and many times that we face issues in this.
So this is a good to know moving on field updates.
I do not evaluate a custom validation tools on fields.
Yeah.
So this is a simple and straight field updates and approval process.
They do not evaluate any custom field of validation rules that we may have e-mail approval response
their assigned approvals is a queue
for this basically how do we Apple Records and sales flows.
We can log into the application and begin apples that are cards.
Yes.
And we can use mobile device to approve records.
Yes.
And the other option would be to use emails to approve records.
So in order to enable users used to email to Apple Records go to the process automation settings setup
process automation settings.
Then you have the option to enable users to use email to approve their.
So if you enable the zoo your option then users can approve or reject records by replying to emails
however there is a catch here.
This option can't be used if the app ruler is a cube here.
Then we try to edit the apple words we have the option of assigning the apples to a cube.
So if the assigned Apple does a q then email Apple will response is not supported.
That is what this is all about.
Email Apple response.
They're the assigned apples as a group basically does not support.
Mass transfer absolute processes we have this feature of mass transfer to other objects that can be
mass transfer records.
Similarly we can also mass transfer approval processes so far transferring the approval records set
up find mass transfer using mass transfer records that shows you you know you can mass transfer records
for other objects.
Similarly you can mass transfer approval process of that so.
So here you have many different options for choosing which are all the records that you would like to
transfer.
So give that criteria find you will have all the processes listed out and then you can choose to whom
you want to transfer those records to so mass transferring approval processes is supported finally Apple
limits to know about that really limits.
Let me quickly pull the salesforce hype page.
So here is a list down the various limits with respect to approval processes.
It says the total approval process thousand per object three hundred and how many approvals can be whatever
how many number of actions we can define in each step and all these we may not be able to have these
numbers on the top of our head.
However it is definitely good to know that limits apply to approval processes so these are some of the
considerations that we need to have while using approval processes and sales force.