Flow to be initiated on a data context and also have multiple instances in same case

User Experience
1

We have a flow with multiple assignments which will be worked by different users. Scenario is on submit of first flow action/assignment, an instance needs to be added to a data object and as the flow progresses on completion on each assignment the same data object needs to be updated. Issue is this flow will be triggered from multiple points on a case. At a time, there could be multiple assignments of this flow will be available on the case, but we need to stick to the data object created for that flow initiated and keep updating it.
Case-ABC

Flow1-Assignment1-DataItem1 created
Flow2-Assignment1-DateItem2 created.

Then
Flow1-Assignment2-Dataitem1 needs to be updated

Flow2-Assignment2-DataItem2 need to be updated.

Most likely this looks like a flow need to be run on a pagelist context kind of but really a split for each use case as we don’t know how many times this flow might get initiated from the case.

This requirement in Pega Constellation in 25.1.2

2

Could you give more details about the business use case? or a version of it if you can’t give specifics.

I’m trying to picture what the business outcome is here. I’m thinking of a Banking Customer, who might have applied for a mortgage, a credit card and maybe raised a complaint - these are all different cases against the same customer - so why not keep them as different cases?

But maybe i’m missing some details here.

Split for each
This still works in Constellation, if you go that path. There was a discussion just today in Distinguishing between assignments with Split for Each shape that you might find useful.

3

Hi @MarcCheong ,
We have a Parent case type A and a Child Case type B. Both of these case types will have a Payment task which has a sequence of actions to be performed like payment creation, approval, acknowledgement and completion. We need to track the status of each payment under each case, so we are trying to add an instance for each payment in a data table and update the status across the task moves from assignment to assignment.

As the case can have multiple payment tasks /flow from local action as well, so there could be more than one payment in progress in the case. To achieve this, on what context do we launch or initiate the flow or should be go a new case type which could be a child for both A and B case types.

4

I would recommend to go with the Child case type since you have a workflow to track for the payment cases and local actions.

  1. Parent Case A
    1. Payment Case (Creation, Approval, Acknowledgement, Completion)
    2. Child Case B
      1. Payment Case (Creation, Approval, Acknowledgement, Completion)

and multiple payments can exist concurrently under the same Parent or Child case, this is a classic candidate for a Payment Case Type.

5

As @RameshSangili said, I would lean towards child cases. However, in the past I’ve also gone the Configuring Actions for data objects - Knowledge Share - Pega Forums route, as the cases were so loosely coupled, it made more sense to have the Entity (data object) as what binds the relationship between our cases together.

It is something you’d have to evaluate how closely all these are linked?

  • Do we wait for child case to resolve to proceed parent?
  • Are there grand children? (children of children) - it may make more sense to split them out so its not a huge complex hierachy?
  • Does one child case impact another child case?