If flow utility shape with ticket is copy-pasted, the ticket-raising does not perform properly.
Errors can vary widely, since the symptom is that a raised flow ticket fails to transfer to the expected place in the flow .
Steps to Reproduce
- Copy a utility shape that contains a ticket
- Delete that utility shape
- Paste back your preexisting utility shape containing the ticket
- Test the flow in a configuration where one of its subflows attempts to raise the ticket. The ticket does not raise.
The copy operation doesn't properly copy the pyTaskTicket list, and therefore the ticket-raising mechanism fails.
This issue is resolved in Pega 7.1.7. As a work around, you can also create the utility shape from scratch.
Published January 31, 2016 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.