Question
Tech Pundits Inc
US
Last activity: 9 May 2022 12:21 EDT
Transfer Assignment using Pega API or Pega DX API
Priority 1 : I like to transfer simple assignment from User1 to User2 or WQ to WQ or WQ to User1 or User1 to WQ
using OOTB Pega API - assignments api.
Input Data: I am passing "Assignment Key" and actionID :"pyTransferAssignment" FlowAction ID.
Request Body: reAssignPage is used to refer the properties in section rule.
Need to have a check if below message format passed is correct?
"content": { },"reAssignPage":{ "pyReassignType": "Operator","pyReassignOperatorName":"Pxx","pyInstructions":"Test", "pxObjClass":"Assign-" }
Error Msg:
|
Accepted Solution
Updated: 3 Jun 2021 3:51 EDT
Tech Pundits Inc
US
@MARIK : As per your suggestion to use FA, i proceed further and built logic, to work accordingly. Thank you.
To summarize what steps it took to achieve this solution.
1. Create Flow Action
2. Create Section - Create Property to hold Operator/WorkQueue
3. Create PostActivity
Step 1: Do Property-Set from Primary Page to Param.Operator/Param.WorkQueue.
Step 2: Call Reassign OOTB activity and pass param.
4. Add this FA as CaseType Local Action to work.
Evonsys
US
You may try to use "Update Case (PUT)". API supports actionID parameter. Using this you can submit any flow action defined on the case. Remember you can't submit an assignment with this approach. You can initiate a flow action on the case.
- Add pyTransferAssignment on your case/stage optional actions
- Call Update Case API with actionID = <<flowaction_rule>>
- eTag is required
- Pass the required clipboard properties & pages (embedded) in request body > content
Hope this helps
Tech Pundits Inc
US
@dp_lagadapati I think clipboard structure i am passing need some inputs . Please have a look on the thread.
Evonsys
US
The clipboard structure varies based on the flow action and the Pega version. What I would is, open the case in the portal, try the flow action, input the values on the UI and save/submit.
use the clipboard/tracer find out what page and properties are being set. Initialize the same from API.
Updated: 1 Jun 2021 0:42 EDT
Evonsys
US
As the error message describes, you are not sending the necessary clipboard properties needed by the flow action. use the content {} page to pass the properties & pages. Consider content is equivalent to pyWorkPage and pass the properties
ex:
{
"c_prop1":"value1",
"page_1":{
"propr2": "value2",
"prop3": "vlaue3"
}
}
Tech Pundits Inc
US
@dp_lagadapati I followed the same . You can see in my Question i have posted my Request Data. reAssignPage is clipboard page. Nothing i need to pass in pyWorkPage so kept content empty.
Pegasystems Inc.
US
@ShivaprasadKatti We had to rewrite that flow action to get it to work with the stateless DX APIs. I suggest you build your own transfer flow action that doesn't rely on "reAssignPage". Top-level pages do not work with DX APIs.
Accepted Solution
Updated: 3 Jun 2021 3:51 EDT
Tech Pundits Inc
US
@MARIK : As per your suggestion to use FA, i proceed further and built logic, to work accordingly. Thank you.
To summarize what steps it took to achieve this solution.
1. Create Flow Action
2. Create Section - Create Property to hold Operator/WorkQueue
3. Create PostActivity
Step 1: Do Property-Set from Primary Page to Param.Operator/Param.WorkQueue.
Step 2: Call Reassign OOTB activity and pass param.
4. Add this FA as CaseType Local Action to work.
Pegasystems Inc.
US
@ShivaprasadKatti Perfect!