Question
Tech Mahindra
IN
Last activity: 22 Apr 2016 3:24 EDT
Flow Removed Status in My Pending Items
There is a production case with status "Error: Flow Removed" in user's My Pending Items. Any idea how to recover this work object to the flow so that user can proceed with action.
Pega version 6.3
Accepted Solution
Pegasystems
US
After you click the assignment on the list, and the flow-removed error appears on the screen, the assignment page and work page will be on the clipboard so you can examine them with the clipboard viewer to make what I mention below more clear.
The flow-removed error means that the normal pxFlow list item that appears on the work object that refers to the assignment object is no longer present. To see one of those, click a healthy assignment, and look at the pxFlow item of the work object (usually in the page called pyWorkPage) in the clipboard viewer to see how there are properties in the pxFlow item that both refer to the assignment object and indicate which shape of the flow is the currently active shape.
Once you understand the above, to make your damaged work usable again, you would need to either create a pxFlow item or delete the assignment object. Each has its challenges and needs to be done carefully. If you delete the assignment object, there will no longer be anything to click on in a list, so there will be no way to resume the work. On the other hand, if you create a pxFlow item, it needs to have accurate values for the properties.
Perhaps a way to see what the pxFlow item should look like would be to make a new work object and run the SAME flow and follow the same path. Assuming that one is healthy, you can look at its pxFlow item to get an idea of what pxFlow item needs to be created to repair your bad work.
After you click the assignment on the list, and the flow-removed error appears on the screen, the assignment page and work page will be on the clipboard so you can examine them with the clipboard viewer to make what I mention below more clear.
The flow-removed error means that the normal pxFlow list item that appears on the work object that refers to the assignment object is no longer present. To see one of those, click a healthy assignment, and look at the pxFlow item of the work object (usually in the page called pyWorkPage) in the clipboard viewer to see how there are properties in the pxFlow item that both refer to the assignment object and indicate which shape of the flow is the currently active shape.
Once you understand the above, to make your damaged work usable again, you would need to either create a pxFlow item or delete the assignment object. Each has its challenges and needs to be done carefully. If you delete the assignment object, there will no longer be anything to click on in a list, so there will be no way to resume the work. On the other hand, if you create a pxFlow item, it needs to have accurate values for the properties.
Perhaps a way to see what the pxFlow item should look like would be to make a new work object and run the SAME flow and follow the same path. Assuming that one is healthy, you can look at its pxFlow item to get an idea of what pxFlow item needs to be created to repair your bad work.
There may be an out-of-box activity for assisting with repairing it, but I would have to find out for you, unless someone else here has the name. /Eric
Pegasystems Inc.
IN
Accepted Solution
Pegasystems
US
After you click the assignment on the list, and the flow-removed error appears on the screen, the assignment page and work page will be on the clipboard so you can examine them with the clipboard viewer to make what I mention below more clear.
The flow-removed error means that the normal pxFlow list item that appears on the work object that refers to the assignment object is no longer present. To see one of those, click a healthy assignment, and look at the pxFlow item of the work object (usually in the page called pyWorkPage) in the clipboard viewer to see how there are properties in the pxFlow item that both refer to the assignment object and indicate which shape of the flow is the currently active shape.
Once you understand the above, to make your damaged work usable again, you would need to either create a pxFlow item or delete the assignment object. Each has its challenges and needs to be done carefully. If you delete the assignment object, there will no longer be anything to click on in a list, so there will be no way to resume the work. On the other hand, if you create a pxFlow item, it needs to have accurate values for the properties.
Perhaps a way to see what the pxFlow item should look like would be to make a new work object and run the SAME flow and follow the same path. Assuming that one is healthy, you can look at its pxFlow item to get an idea of what pxFlow item needs to be created to repair your bad work.
After you click the assignment on the list, and the flow-removed error appears on the screen, the assignment page and work page will be on the clipboard so you can examine them with the clipboard viewer to make what I mention below more clear.
The flow-removed error means that the normal pxFlow list item that appears on the work object that refers to the assignment object is no longer present. To see one of those, click a healthy assignment, and look at the pxFlow item of the work object (usually in the page called pyWorkPage) in the clipboard viewer to see how there are properties in the pxFlow item that both refer to the assignment object and indicate which shape of the flow is the currently active shape.
Once you understand the above, to make your damaged work usable again, you would need to either create a pxFlow item or delete the assignment object. Each has its challenges and needs to be done carefully. If you delete the assignment object, there will no longer be anything to click on in a list, so there will be no way to resume the work. On the other hand, if you create a pxFlow item, it needs to have accurate values for the properties.
Perhaps a way to see what the pxFlow item should look like would be to make a new work object and run the SAME flow and follow the same path. Assuming that one is healthy, you can look at its pxFlow item to get an idea of what pxFlow item needs to be created to repair your bad work.
There may be an out-of-box activity for assisting with repairing it, but I would have to find out for you, unless someone else here has the name. /Eric
Tech Mahindra
IN
Hi Osman/All,
For me, the above appears as risky options considering my work flow.
As per below, the mapping (linking) between assign-worklist and work item was damaged.
Why cant we update assign-worklist record, so that mapping is set right.
https://mesh.pega.com/meshvideos/5966
best regards,
Satya
Updated: 21 Apr 2016 3:06 EDT
Tech Mahindra
IN
Team,
Good morning!!
There is a non-sync between assignment record and work class record. Can you please advise with a out of box activity to repair this.
Main Flow Assignment 1 --> Main Flow Assignment 2 --> Subflow Assignment
** this means Subflow is being called in Main flow after "Main Flow Assignment 2" completed
When "Main Flow Assignment 2" approver tried to submit form, somehow data was not updated to database, but a new errored assignment record created which is pointing to Subflow Assignment.
Currently, Work class record has "Main Flow Assignment 2" data. Where as Assignment record got errored and has "Assignment in a Subflow" data. Hence "Assignment in a Subflow" approval could not take action as "Error: Flow Removed" error displayed.
I need to bind the assignment to "Main Flow Assignment 2".
I am trying to write an activity to delete existing assignment and insert a new assignment record with "Main Flow Assignment 2" data.
Team,
Good morning!!
There is a non-sync between assignment record and work class record. Can you please advise with a out of box activity to repair this.
Main Flow Assignment 1 --> Main Flow Assignment 2 --> Subflow Assignment
** this means Subflow is being called in Main flow after "Main Flow Assignment 2" completed
When "Main Flow Assignment 2" approver tried to submit form, somehow data was not updated to database, but a new errored assignment record created which is pointing to Subflow Assignment.
Currently, Work class record has "Main Flow Assignment 2" data. Where as Assignment record got errored and has "Assignment in a Subflow" data. Hence "Assignment in a Subflow" approval could not take action as "Error: Flow Removed" error displayed.
I need to bind the assignment to "Main Flow Assignment 2".
I am trying to write an activity to delete existing assignment and insert a new assignment record with "Main Flow Assignment 2" data.
Eric: Could you please let me know if I need to update/add a record in any table after adding a record in worklist table. Is pxFlowKey in worklist table is refering in any other table. I think database ER diagram will help me to know the table relationships.
Thanks in advance
Tech Mahindra
IN
Hi Eric,
I have replaced worklist record through an actitvity. It worked fine.
I found FlowInsKey in worklist record and current pxFlow need not be same. Is my perception correct?
Best regards,
Satya