Mostly asking from a devil’s advocate perspective, but why would multiple policy approvals be required? Is there not an approver that can serve as the “buck stops here” approver? Could part of their approval duties be that they are required to gather all other necessary approvals and store elsewhere (since Eramba won’t do for that), but the key control is their approval rather than a group?
As referenced in the 2.6.0 release notes, workflows of some sort are in the pipeline for prior to the end of the year. Exactly what that will entail, I’m not sure - maybe @eramba can point us to the thread that’s being worked for it and whether it would be applicable in this scenario (looks like #389 “User Defined Workflows”)…