Close popover
Sharath Chandra Kalahasthi (SharathChandraK2566)
Capital One

Capital One
SharathChandraK2566 Member since 2019 1 post
Capital One
Posted: December 4, 2020
Last activity: December 5, 2020

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.

Pega Platform 8.4.1 Case Management Financial Services Lead System Architect