Implement project role based custom approval hierarchy using AME - part 5 - Approver Group

The reason our second test only returns "Director" employee instead of including everyone below him/her is caused by our query. We did an exact match to the project role "Director". To fix that, we can use a more complex query or using AME:

• Nested group can be used to remedy the situation. Create a nested group called "Director" level, then add "Manager", "Operation" and "Director" approver group to it. You'll get all three approvers without additional coding. 

• One minor detail: order number plays an important role in arranging the approvers in the list --> The lower the order number, the earlier an approver appearance.