Question
Morgan Stanley
IN
Last activity: 15 Sep 2024 2:25 EDT
Flow completed using Tickets does not clean up pending tasks in Assign- table
Hi, I have used a Ticket to complete a flow. This ticket is set from an Agent activity and it is working fine. Flow is resumed and case status chnages to "Resolved-Cancelled" however I can see the open tasks of Assign-WorkBasket class is still present in the DB table.
Can someone please confirm if set ticket doesnot remove the assignment or it only resumes the flow ?
Accepted Solution
Updated: 15 Sep 2024 2:25 EDT
Bits in Glass
IN
@SnehasisP0085 ya correct. Usually resolve stage will be there where we enable delete open assignments. But in these kind of scenarios we would need to manually delete assignments.
If we have a scenario where we have a flow with assignments or subprocess which has assignments, then based on some logic if we need to complete the flow without opening assignments, then we can directly call ticket.
But in your scenario, ticket is being called after the assignment is opened to complete the flow. So here we need to delete assignments using activity. Instead of ticket if you use pxForceCaseClose, then we have parameter for deleting open assignments.
Pegasystems Inc.
CA
Could you please confirm that the cleanup process is enabled in the resolution stage?
Thanks,
Ramesh
Morgan Stanley
IN
@RameshSangili Thanks for responding. No, clean up process is not enabled and cannot be enabled as our case type does not have any stages it is only a flow based case type i.e. pyDefault rule has only the starting process flow, once this flow ends the case worflow ends.
Bits in Glass
IN
@SnehasisP0085 you can try using pxDeleteAssignment in this scenario.
Morgan Stanley
IN
@Anoop Krishna Thanks Anoop, it seems PEGA tickets only resumes/jumps the flow processing, it does not clean up the pending tasks. Developer has to manually take care of open assignments when using tickets for flow processing.
Accepted Solution
Updated: 15 Sep 2024 2:25 EDT
Bits in Glass
IN
@SnehasisP0085 ya correct. Usually resolve stage will be there where we enable delete open assignments. But in these kind of scenarios we would need to manually delete assignments.
If we have a scenario where we have a flow with assignments or subprocess which has assignments, then based on some logic if we need to complete the flow without opening assignments, then we can directly call ticket.
But in your scenario, ticket is being called after the assignment is opened to complete the flow. So here we need to delete assignments using activity. Instead of ticket if you use pxForceCaseClose, then we have parameter for deleting open assignments.