This content has been marked as final. Show 1 reply
I've successfully implemented AME and would like to share some insights.
- Approvals using Position Heirarchy is Limited, Linear and Striaght-forward. It does not support flexibility and complex business cases.
- AME gives the developer/business analyst full control of who you want to be an approver, it could be "hardcoded", or dynamic from a query.
- AME also gives you control to grant separate approvals in lines and headers, making it parallel and split into how you want it.
- As I've used, i've actually just enhanced Position Hierarchy rather than substituting to AME. i used position heirarchy, person and position to map out approvers.
I've realized the power of AME and how it can really improve document approvals.
hope this helps!