Is it possible to jump from one flow to a specific point in another flow using Tickets ?
My requirement is that when one of my flows end, I have to jump to a specific point in another flow. I know we could use tickets to jump/skip steps within a single flow. Would this tickets concept help me in jumping from one flow to another ?
As of now I have included a utility shape before the end shape and set the ticket with the 'SetTicket' method. The ticket name that is mentioned here, I am setting in the tickets section( in properties ) in my destination flow...in a utility.
***Updated by moderator: Lochan to update Categories***
Are you using stage based case management? If so you can easily jump between stages using OOTB API like pxChangeStage rt. You can move between primary and alternate stages and use when conditions to skip certain steps/flows
You can do this using Tickets. Even you can invoke a ticket in Parent case or child case too. However as far as i know this API is old and same can easily be done with OOTB API rules like above
I am using case management, but I have only one step in each stage and I am calling a process(flow) in that first step.
This lauches the flow and all my tasks in that stage are done. Similarly, the next stage will have only one task/step under it and I would call a process/flow for that stage and the work is done.
I am not able to mention task by task under each stage as a default flow will be auto genearted and I would need extra flow shapes like utility that i cant find in the default options of steps under a stage. So I make a flow according to my requirement and call the flow as the first step under the stage.
Is this the correct way of implimentation? Request you to kindly confirm.
Posted: 5 years ago
Posted: 28 Jul 2016 6:05 EDT
Durgaprasad Lagadapati (Prasad_Lagadapati)
Sr. System Architect - Pega Consulting
If you use PRPC 7.2 you have several options while creating steps in case type.
However you can use all of these utilities/shapes inside the flow. I can not comment on your design but making flows more modular (breaking into reusable components) always is better than having 1 flor rt.
Coming back to your actual question of using tickets- In your flow where ever you need you can call this activity "SetTicket" using an utility that fires the ticket. On the target flow you need to configure the ticket like below