Auto approve approval based on field and decision table

Casper6060
Mega Sage

Hi Everyone

 

I have a requirement that if a field called Auto Approve on the Change Request form is set to true, and my decision table evaluates to true, then auto approve any approvals that might be generated.

 

If possible i would like to have this running inside flow designer so others can easily change the setup if required.

 

Now i have this working already by creating a flow on the sysapproval_approver where it triggers when an approver is created where the relationship to a change request is not empty and that change request has the field auto approve set to true.

 

Then i get the different record counters for my decision table and then determine if i can actually approve the approval or not.

 

Now the issue here is if the change request has 13 approvals. Then the flow will run 13 times, which could be a waste of resources.

 

Does anyone know of a way to run this from the actual change request and then run through the associated approvals.

 

Because from i can see there is no way to trigger a flow when an approval is added to a record?

1 ACCEPTED SOLUTION

Casper6060
Mega Sage

To anyone who might one day look at this, the answer was that no there is not a related record / relationship trigger (i used to work with Cherwell Service Management) where this was possible.

 

If the relationship is a 1:1 then you can do it no problem, but if it's a 1:Many relationship, you cant set the Many table as a trigger, so either you have to make sure something is update on the parent table everytime a record is added or update on the child table.

Or you do the workaround i did and put your trigger on the Many (child) table and have it run from there.

View solution in original post

1 REPLY 1

Casper6060
Mega Sage

To anyone who might one day look at this, the answer was that no there is not a related record / relationship trigger (i used to work with Cherwell Service Management) where this was possible.

 

If the relationship is a 1:1 then you can do it no problem, but if it's a 1:Many relationship, you cant set the Many table as a trigger, so either you have to make sure something is update on the parent table everytime a record is added or update on the child table.

Or you do the workaround i did and put your trigger on the Many (child) table and have it run from there.