Note: It is a Headless Pega Application.

Hello,

Is it a complex flow you having with a lot of assignments? I think I would add those information to the WorkObject unless this is too much. You can add a specific page to store those information and retrieve them at the right time maybe.

If this is too much information to be stored on WorkObject then you will have to save all that on a dedicated table somewhere else.

This will require custom configuration anyway to be executed at runtime during this flow execution either with utilities or post activity on flow actions.

Hi There,

I have an idea. You could use the case stage dashboard to figure out these things.

You can inspect how it is getting the cases details. There are OOTB data pages eg:

D_AllCasesInApp.pxResults

D_CaseStageCount

You can use these data pages or create your own DP on similar lines with you requirement.

Now, Pega api exposes service to directly get the data from the data page. You can use that OOTB way to provide the requested service.

Hope this helps.

Hello,

I'm not sure I 100% follow your requirement, but is this not captured in the work object history? You may have to filter to just get the assignment data you want, but the data should be there. 

If you're only worrying about active assignments, the pxFlow page should have all of that data for you since that is essentially the call stack for every open assignment. It won't tell you exactly which path you took in the flows if they are complex, but FlowA, called FlowB, called FlowC, etc is there, as well as the shapes in the flow to return to as the stack unwinds.

Thanks,

Mike

i think you have to write an activity(your logic will be browse on work table and fetch all open and Pending assighnments) , use this activity in your service.