Question
Bank of America
US
Last activity: 5 Dec 2020 2:57 EST
case type and flow use case
Hi All,
Looking for a good design solution. The application is headless(no UI) and the case is run by an standard agent. Given, we know the number of approvals that case will have to be routed in its life cycle. ** it will have to be routed sequentially.
The steps in flow is:
1. Case will call a service call, if successful route to work basket
(Case will wait for approval now which happens outside Pega. Through REST call the case would resume the flow.)
2. Next, the case will call same soap call with a different request parameters. If successful, It will be routed to work basket 2 or keep retrying the service call.
So on.. and so forth...
Requirement is, instead of calling the above steps 1 and 2 each time, how to configure flow once and repeat the process twice.
(** as Split-for-each will execute independently one after the other without waiting for 1st work basket approval, unable to achieve using that.)
The number of approvals will vary for different cases, so trying to configure the flow to execute dynamically.
Accepted Solution
Updated: 5 Dec 2020 2:57 EST
Bank of America
US
Hello All,
I found the solution for the above use case.
I am able to customize cascading approval feature by saving extension flow “pyCascadingGetApproval” flow into our ECS and running the service call before routing to each of the approvers.
FYI,
One bonus I found is we can even route it to work queue by handling that in the pyCascadingGetApproval flow and assigning approves list to work queues.