Unable to Transfer work object from one worklist to another worklist using pxTransferAssignment OOTB Rule
Hi,
I am trying to transfer WorkObject from one worklist to another worklist using pxTransferAssignment OOTB Rule but getting Error.
Steps fallowed:
1. Property-Set:
1.1: local.AssignmentID="Given pzinskey of WorkObject".
1.2: local.RouteTo="Given Destination Operator ID worklist".
2. Calling pxTransferAssignment and passing the above variables.
I found this URL: https://collaborate.pega.com/question/pxtransferassignment-ootb-rule-not-found-exception and tryed the same thing. Attaching the error below.
Please tell me how can i achive this using pxTransferAssignmen or any other ways to do.
Thanks in Advance..!
Pegasystems Inc.
FR
Hello,
You cannot transfer a WorkObject., you can only transfer assignments. And this is your error here. The system is having a Work- page to work with instead of Assign- page
Updated: 7 Jul 2020 0:20 EDT
e-pragati
IN
Thanks for the reply.
My scenario is, Customer submited a request form and that WorkObject say R-123 routed to a Employee(Head of the section) WorkList, whose action is to approve or reject. Based on the employee action taken case gets resolved and completed. Now the employee left the organization. So i want to asssign this assignment to a new employee WorkList so that he will approves or reject the case. How an i achive this.
Please suggest me a solution.
Thank you..!
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
Please find the below article, similarly you can pass "Worklist" and username as a parameter.
https://collaborate.pega.com/question/route-assignment-work-basket-using-activity
Else we can also use the "pyTransferAssignment" flow action to transfer to an operator from the case itself.
Pegasystems Inc.
IN
Hi,
You can try giving the local.AssignmentID as pzInskey of the assignment(which is present on newassign page)instead of pzinskey of the work object
e-pragati
IN
Hi yerrh, Tryed the same thing but getting this error message"
trying to calculate the handle of a class whose instances may not be written to the database: Assign-: code: SQLState: Message:"
Here I am attaching error message and activity written. please correct me where i have written wrong.
Tata Consultancy Services
IN
Hi @ravip410,
I am also getting same error. Please help me to resolve issue..
Regards,
Shailendra Mishra
Updated: 23 Mar 2022 8:01 EDT
Pegasystems Inc.
GB
@Shailendra Mishra this thread is a year old and was for Pega 7.3.
Are you using pxChangeStage?
The error has been known to occur when a local action is being run in a modal. The SubmitModalFlowAction activity is creating newAssignPage with the class Assign-. You can add a couple of steps to your activity to rename newAssignPage temporarily.
Please test the following steps:
- Call Obj-Refresh-And-Lock to get the lock of the Work Object.
- Rename newAssignPage to TempAssignPage.
- Call pxChangeStage. Define ChangeToStage parameter and CleanUpProcesses set to true.
- Call WorkCommit to persist the changes.
- Rename TempAssignPage to newAssignPage.
- Also refresh the harness or sections as needed as the modal dialog would be closed and harness/section might not be showing correct details.
I suggest that you post a new Question
In the new question clearly stating the Pega version and method you are using, and the symptoms and error you are seeing.
Please state what troubleshooting you have carried out and provide a screenshot in your new Question.