I understand that cases are sent to the Broken Process Workbasket when their routing information is incorrect. I would like to know why the Broken Process Workbasket exists in the Pega platform and how we can make use of it. Additionally, I would like to inquire if it is possible to delete the workbasket if it cannot serve any useful purposes.
Hi @IwasawaM16662753: As you rightly said, the case will be routed to Broken process Work basket when there is a issue in the flow (like routing info not available). Can you help us to understand why do you need to delete this workbasket? Deleting this will cause the exception handling to fail. This is not a right choice.
You can override the workbasket for broken process but it is always good to keep the work basket in system.
Thanks.
Hi @IwasawaM16662753, suppose you have an assignment which goes through a flow & there within is a decision shape but none of the conditions evaluates to true, your case will be routed to the Broken Process WB.
Now, suppose you find out the reason because of which none of the conditions were valid and you fix it by adding a new condition in the flow. If, you then try to resume the same work object which had failed earlier you’ll be able to proceed further.
Thus, having the workbasket here helped in retaining and progressing of the case & that is why they are important. If in case you didn’t have this basket, your case would be lost & could never be recovered.
@IwasawaM16662753 You need to override the activity getFlowProblemOperator in the work- class to your application workgroup class and then you can set it to other apart from brokenprocess workbasket which is been set by default by pega.
@ArulDevan and all
Thank you for the reply. I understand the reason of the existance of the BrokenProcess Workbakstet and how to solve my issue. Our system had some problem related to this WB that we will discuss how to deal with issue with our team member with the provided information.