Implement project role based custom approval hierarchy using AME - part 2 - design decision

There are many different ways to approach an issue, here are some of considerations on custom hierarchy:

• Flexibility: Can you handle custom hierarchy based on totally different criteria after initial implementation? Eg, using PO Purchasing limit
• Scalability: Can you add new companies, project types, budget types after initial implementation?
• Maintainability: Can you modify approval hierarchy after initial implementation? Eg regression testing
• Worst case scenario for number of custom hierarchy = Company * project type * budget type.

                   Eg, 4 companies each uses 2 project type and 2 budget type and different project roles will have  4*2*2 = 16 custom hierarchies.

Approaches considered:

Not feasible:

• Embed approval hierarchy in the PA Workflows