See the screenshots below. I have a form configured to run the Start Approval Route action upon completion. When the form has tripped a single group-based role, the code thinks that there are no approvers, so the route is not started. Going to the stage and running the Start Approval Route action works as expected.
Workflow Rules Tripped Group Task:
Workflow not started notification
Tested on qa2 (ACA 3.4.3), but I would bet that edge/release have the same issue. We should test this scenario as well as one where a user and group role are tripped (same priority and different priorities - group first as well as user first).
See the screenshots below. I have a form configured to run the Start Approval Route action upon completion. When the form has tripped a single group-based role, the code thinks that there are no approvers, so the route is not started. Going to the stage and running the Start Approval Route action works as expected.
Workflow Rules Tripped Group Task:
Workflow not started notification
Tested on qa2 (ACA 3.4.3), but I would bet that edge/release have the same issue. We should test this scenario as well as one where a user and group role are tripped (same priority and different priorities - group first as well as user first).