Action based on approval feedback

Question

Hi team,

I have a business rule which is triggered, after an approval request was updated.

• Is it possible to read the reason somehow (if entered by the approver)?
• Is it possible to run these actions only against specific approval or commands which create approvals?

Comments

Hello,

If you have a business rule configured for the ApprovalRequest object type (e.g. triggering After updating a ApprovalRequest), you can obtain the reason for denying or cancelling the request using the below code:

$reason = $Context.targetObject.DenialOrCancelingReason

The below code will obtain the reason for approving a request:

$reason = $Context.targetObject.ApprovingReason

Is it possible to run these actions only against specific approval or commands which create approvals?

Sorry for the confusion, but we are not sure what exactly you mean. Please, describe the desired behavior in all the possible details with live examples.

---

Thanks for your answer.

I tested your shared script, and it has the same value for approving and denying a request.

I also found this variable, holding the same information.

adm-DenialOrCancelingReason

---

Sorry for the confusion, but we are not sure what exactly you mean. Please, describe the desired behavior in all the possible details with live examples.

Right now my business rules looks like this

This means, it would be triggered against all approvals, no?

I would like to narrow down it further, so this should be only executed if an approval was initiated by either one specific custom command or business rule.

Answer 1

Hello,

I tested your shared script, and it has the same value for approving and denying a request.

Thank you for pointing out the issue. We forwarded it to the corresponding department for consideration.

Right now my business rules looks like this

Thank you for the provided screenshot. The business rule should work just fine.

This means, it would be triggered against all approvals, no?

Yes, that is correct.

I would like to narrow down it further, so this should be only executed if an approval was initiated by either one specific custom command or business rule.

Unfortunately, there is no such possibility.