Question
United Health Group
IN
Last activity: 4 Oct 2018 13:54 EDT
how to delete assignment after case is resolved
Hi
In our application work object is resolve cancelled, still assignment is stuck in workbasket. how can I delete that?
I tried pxdeleteassignmentforwork. since pxflow dont exist this did not work. can you please help me to delete the assignment from workbasket? not from Database, but from application
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
US
If there is a Flow Removed error associated with the assignment then it should show up in the Workbasket Assignment Errors report, which has an option for deleting the assignment. If this is happening consistently then you will want to review the steps taken when resolving the case to understand why the assignment is not being removed as it should.
United Health Group
IN
Hi Wenhardt
Thanks for the reply. flow removed error is not associated with the assignment, hence not listed in workbasket assignment errors.
Pegasystems Inc.
US
Interesting, if someone tried to process the assignment but the work object was resolved I would have expected a flow removed error. What happens when you try to open the assignment from the workbasket?
If needed, you could also write your own activity to open the assignment and delete it.
United Health Group
IN
we dont have access to open it. now the work object got deleted how can I restore it.
Pegasystems Inc.
US
If the work object was deleted from the database, you would only be able to restore it from a backup.
Accepted Solution
Pegasystems
US
Normally, work objects are not deleted at all, and as the flow advances from one assignment shape to another, the Pega core layer handles the deletion of the assignment objects.
If you've got some situations in which the assignment objects are being deleted, and other situations in which they are not, please compare them, perhaps even by comparing traces, to see why they differ. In particular, identify the place in the good scenario where the core layer is deleting your assignment for you, to help figure out why the logic in the bad scenario is either not reaching that place, or is, but is failing to delete the assignment properly.
And find out why your work objects are being deleted. Normally they wouldn't be. /Eric
Accenture
IN