No Actions prompt under the workobject Actions bar
No Actions' is being prompted while trying to open a workobject (assignment). When queried on the Pega database, the assignments are neither seen in the worklist or workbasket. In addition to that, the workobject assignment has neither seen at 'Worklist Assignment Errors' or at 'Workbasket Assignment Errors' so unable to restore the assignment. No exceptional logs were observed w.r.t to this issue and this issue is sporadic in nature and this issue was observed only when trying to route the workobject to a workbasket
Have you looked at the work object's pxFlow page? That is essentially the work object's call stack, so assuming the item isn't resolved, you should be able to reconstruct the assignment if it's in there. If it's blank/has no open assignment pages in the pagelist, I would start by looking at the work object's history to try and understand how it got into the state.
Thanks for your reply Mike but in this case we observed that assignment has been removed from both worklist and workbasket and in addition the audit is not giving any trace about the last assignment status and the workobject is not resolved either so is there any way where we can reinstate the case to resume its work flow?
Apart from worklist,workbasket and history tables, is there any way to get more details about the current assignment status ?
When dealing with assignment errors, I typically look at the history for a few of the work objects where the issue occurred to see if there is a pattern. For example, did an agent or some other process run, after which the assignment was missing?
You can look at the Suggested Approach section in the article below for steps on how to resume the flow at a particular point to recreate the assignment.
Thanks for the reply Carissa. In this case, the workobject hasn't been routed to problem flow but its just that the assignment has been removed and No Actions is being displayed. Can you confirm if we can use RetryProblemFlow activity to reinstate the assignment ?
If the flow is listed in the pxFlow page on the work object, then you should be able to use those steps. If there is no pxFlow page present, then you can call StartFlow in the activity instead of RetryProblemFlow.
You can test it out by creating a test work object and using an activity to put it in the broken state. In your activity you can open the work object, remove the pxFlow page if that is what you see in your work object, and delete the assignment. Then you can go through the steps to test repairing it.
As attached in the snap, I can see the pxFlow page on the work object but to try RetryProblemFlow activity, I am not sure about the FlowStep param value. Can you please confirm me on the following queries:
1) Does the property value of pyFlowType on the pxFlow page can be passed as FlowName param for the activity RetryProblemFlow ? If not can you please suggest of how the value can be obtained ?
2) Does the property value of pyLastFlowStep on the pxFlow page can be passed as FlowStep param for the activity RetryProblemFlow ? If not can you please suggest of how the value can be obtained ?
When calling RetryProblemFlow, you would pass in the flow name and the step you want to resume. It may be pyLastFlowStep but not necessarily. If you want to start from a particular assignment you would enter that flow step. You can look at the XML for the flow rule to get the flow step. It will be in the pyMOId property for that shape on the flow. For example, in my case I only had one assignment and the pyMOId was ASSIGNMENT63.
Thanks for your help and now, I am able to reinstate the flow of the workobject by using the 'RetryProblemFlow' activity however I can see couple of duplicate options being shown when I clicked on the actions bar of the harness. Probably, it could be a default behavior of Pega where the first option from the navigation is prompting 'No Actions' and the second option from the navigation is prompting the actual and required assignments to load. Please confirm on this behavior(if its valid and expected).