Posted: 24 Jun 2016 14:34 EDT Last activity: 13 Jul 2016 2:21 EDT
Explanation of Tickets and Appropriate Usage in a Flow
Hello Pega People,
I am having difficulties understanding what tickets are and how one correctly implements them in a flow.
I have read that tickets behave similar to GoTo statements used in Prorgamming Languages.
What I don't understand is how to implement one.
For example if I had a flow where I do assigments and other shapes and then following the natural line of the flow it takes me to a setTicket shape where I set a ticket to the name of a section I wish to go to (lets say Section1), will this setTicket shape then automatically jump over all the flows infront of it and make it to the Section1? (Or jump back in the flow and make it to Section1 if that where the case).
I also fail to understand what the condition for the GoTo would be. How do I define that I only want to GoTo Section1 if one of my parameters is equal to 109 for example.
As you may see guys I am struggling,
Any help is appreciated greatly!
Share this page
Moderation Team has archived post,
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.
Ticket Concept u can compare with the Jump to later step in the Activities.
If I understand correctly ticket Shape will come as Triangle on top of the assignment when you set some ticket on that particular assignment shape.That means you are creating some destination point for the control to be reached when some body set this Ticket using the SetTicket OOTB activity.
We generally use the "USE ALTERNATE STAGES " in order to make our flow jump to the other assignments in other flow.which can be configured on a flow using "change stage "shape.
Tickets are generally used when you want to jump your flow to a specific shape of a child class.you can even do that by alternate stage.but still if you want to achieve it ? then
we do a set-ticket in an activity or on any shape of a flow and give the reference of a ticket name and refer it on the assignment that it must jump to.
generally tickets are used for easier access but not suggested approach.if you fail to do by a alternate stage then you go for it.
say for eg:
i have a requirement that if a person is married and then clicks submit he must go to married details.
for this:i have a flow with a subflow.the flow follows the happy path strategy.now i wanted the subflow to be executed only if the user selects the option that he is married. the married flow is an assignment in the subflow which executes after 10 assignments till then i don't want to do a series of submits. For this what i do is :i use a change stage shape and jump to wherever i need or i can use a ticket on one of the shapes on my main flow assignment shape.where it verifies for IsMarried condition and if satisfied? then we give a ticketname both on the assignment shape on the main flow which it must jump from? as well as on the subflows's assignment where it must jump to?