Two tickets on two dangling end shapes not working
We are developing out application in Pega 7.1.8.
The flows are complex and we have to use tickets to jump to multiple steps in flows.
There are few flows which are having 3 end shapes. Out of these 3 end shapes 1 end shape is connected to other flow shapes with connector. Other two end shapes are isolated (not connected). Each of these isolated end shapes have a different ticket on it.
e.g. EndShape1 has ticket EndSMS ticket and EndShape2 has a 'Resoved-Dead' ticket.
When we are raising ticket 'EndSMS' in an activity using Call SetTicket then 'Resolved-Dead' ticket is getting set. This behavior is very inconsistent. At some places by removing ticket, adding it back, removing cache it started picking up correct ticket. But this work around is not always working.
Can anyone provide some pointers here? Is it prohibited to have multiple end shapes with separate tickets on it.
In our application we can not use same ticket names on both end shapes or create a single end shape due to functional complexities.
Regards,
Aniket
Pegasystems Inc.
US
Aniket,
Hi. It sounds like what you are doing should work, but it might help if you added a screen shot of how you have the tickets connected to the end shapes. Also, I don't know if I understand what you mean by "removing cache". What cache? How are you removing it? Are you saying the wrong version of the flow is running and this makes the correct one get called temporarily? Looking at SetTicket, I see that the save of the removal of the ticket won't be called if you have a temporary object, have no pzInsKey, or the primary page of the activity has messages. Could any of this be the case?
Thanks,
Mike
Vodafone GmBH
IN
Please see above image. If in an activity I am doing a setTicket on SMSEnd or Cancel still it picks up the Resolved-Dead ticket.
This is happening in multiple flows. For few flows after deleting Rule cache it worked. But for few others its failing.