Now let's analyze a business scenario that maybe be using process builder to exude by independent actions.
Basically no previous videos we did about the immediate actions actions that happen immediately when
the process is good.
But now let's try to configure time dependent actions.
So for others let's consider a business use case then not a department record gets created.
So department here is basically a custom object that we have in case you do not have the customer object
you can try to create a new one or you can use any of the standard objects that you have so whenever.
But I can't get created with 9 department details department details is basically a fee that we have
in that object.
So then we created a cart with a nice value in that particular field.
Then watch your happiness update the field with the department name and department code.
So the Department details should be updated with the name and the code after one day.
So that does not immediate.
Basically after one day.
So there is a dependency on time here.
So whenever we have scenarios written like we have this time dependency that time we go for this time
independent actions and process through the in fact this is just one scenario that we are talking about.
Well for this time dependent actions we can call them for real time scenarios.
Say for example consider the opportunity object of vigor we may have a scenario but and we need to send
out the any reminder emails 10 days before the opportunity to state if the opportunity is still open.
So say for example the opportunity close Data's next month and before 10 days prior 10 days.
We need to send a reminder email to the opportunity owner saying that the opportunity is to be closed
within 10 days.
But it is still open or maybe we can use this time dependent actions for recreating somebody's mind
a task or a follow up task.
So say for example if some rep is not assigned to do an account order if some activity is not closed.
So that are the number of business scenarios bit and we'll be using these as scheduled actions.
So I'm I'm back.
We have just picked one scenario and using the scenario we'll understand how little we can figure out
this process.
The
never liquidation process builder let's create a new process
fill in the details
have just copied the same to the description but yeah please give it a lot better description
and now let's configure this object and we'll also specify wrinkles start the process the object here
is the department Custom Object
and here we have two options one has been that a guard is created the other has been that a guard is
created or edited.
So then we use this scheduled actions that is our time dependent actions the option of this time dependent
actions that does the schedule of actions as you see here is available only then the record is created
it will not be available then the record is created or edited it say for example like I choose this
option let me save this we have this right did we have the option of adding scheduled actions how violent
if we choose the other option then that a guard is created on Ed then we do not have that option of
adding Skidoo with actions but still we can still add scheduled actions when the criteria is created
or edited in the criteria section Soledad let me add the criteria and then I'll show you that no information.
So let's add the criteria for the time being I have a desert a guard is created that does a lot of business
use case save it and the criteria the criteria here is the department details is night so I have added
the criteria name and let's say the conditions
department betas have chosen the field use Nye set to true.
So this is our criteria.
All right then this criteria is satisfied.
Then it goes for the actions.
So we have defined the criteria as what and as I mentioned before the scheduled actions are available
only then that a court is created right.
But then the record is edited.
We know the scheduled options is not available.
However we can make it available under one condition.
We have this option of advanced in criteria in criteria.
We have this option that it is saying do you want to execute the actions we'll leave unspecified changes
I made to that.
Basically meaning only even this change happens.
This process will fire so before back it should be a different value.
And this change should be the specific change for this process to fire.
That is the meaning of this.
And that is what is given in this.
And a you select this option then you will get scheduled actions.
So basically there are two scenarios in which you will have collections.
One when you start the process only then that a guard is created or then that account is created or
edited.
And also you choose this option on that criteria so under these two conditions you would have the option
of adding scheduled actions to your process however this is just for the information but ask but other
business use case it is on creation.
So let me choose the first option and I'll save this.
I just wanted to show you both the scenarios within the scheduled actions will be available.
That is why I changed it.
But ask put our business and that it is only when the department record gets created.
So that we have updated that back to created and here and here you have and it is created you will not
have that option also in criteria that advanced option that you had that option.
The Lord be present when you choose the created option only created option perfect.
So now we have defined our criteria.
The Department details is nigh full effect save.
And now let's add other scheduled actions so forth do and actions first let's set the time.
Say one day after create a date meaning after one day after the department that a guard was created
then the department these days I should be updated with a name on the court.
And as you can see there are multiple options out here meaning you can define multiple schedule that
actions here similar to immediate actions immediate actions also begins.
Could do it multiple immediate actions similar at least get to our actions also you can create multiple
actions.
So now that we have configured our time let's define our action what has to happen.
The action is updating that glass we have to update the department glass
so our action name is update department details and we need to say select the department guard.
That started the process.
We just need to update the same record not any child that I got off that glass so I'm choosing this
option and then no criteria.
Yes all the cards.
And here we need to set the field values the field value is the department details should be appended
with the the code and the name.
So the Department of Defense I should have both the name and the code so for populating this field value
with more the name and the code go for the type formula.
We have four options out of this juice formula specifically to show you all these options.
I chose this requirement.
So let's go for formula here.
And here we have the option of building the formula so let's say
department name basically does a string and let me concatenate this that the field value that does that
and their department name
so department name.
This is just a plain text and then it pulls the value from the Department assets from the named field
and then let me again concatenate this
and then department called
and pulling the field ass way the department code.
So this is a very simply formula I have concatenated some next.
And also the Ft.
So once you have done all this click on use this formula the formula gets uploaded here and then save
full effect.
So now we have configured let's do elections.
We have defined the time.
Basically that is one day after create date after the department record God gets created.
And we have also defined the action what needs to take place.
So now that we have a completely done with the configuration activity process gone from
no for testing this process what we need to do is we need to create a department a guard with a night
a department details and then once you save it this process will get triggered and automatically the
scheduled actions happen and the actions happen basically after 24 hours after the created date.
So to model if you check the department details will be updated with that name and the code as it has
guard the time dependency I'm unable to show you the output but still it is pretty straightforward and
you yourself can go and test it out.