I am creating case and moving forward by performing flow action from Service-SOAP. I used svcAddWorkObject to create case and svcPerformFlowAction to move case forward. Please refer the attached screenshot of Service activity and it's running in MyServicePage context. Case is creating as expected but getting "RequiredParameter flowName" error message from performFlowAction activity in step# 3.
Please share your thoughts on this, correct me if something is missing.
The param.FlowName that you are setting in this activity is used to do performFlowAction only if the WorkHandle is passed. In your case you are passing AssignmentHandle so this means svcPerformFlowAction tries to open the assignment and gets the flowName from AssignPage.pxFlowName. This is happening in the 11th step of svcPerformFlowAction. So please check if your assignpage has the correct FlowName populated after the work object creation.
Thank you for your thoughts. Now it is working after changing parameters like in attached one (Params.png).
Now I'm facing another issue,
- Case created svcAddWorkObject, work parties are created as defined in case definition.
- Flow action performed by svcPerformFlowAction, it should be moved to next assignment configured with ToWorkParty routing activity. It got assigned to Administrator saying no routing information instead of given work party parameter. Because pyWorkParty(Manager) is not presented when routing activity is executed.
- pyWorkParty(Manager) on pyWorkPage is there properly when case is created. But svcPerformFlowAction activity -->acquireWorkObject activity step#10 is merging MyServicePage into pyWorkPage. Here pyWorkParty pages are deleted.
- To avoid this, I tried to call svcPerformFlowAction with pyWorkPage as step page, but error (The workPage can't be the same as the mergePage.) is coming from step#2, acquireWorkObject.
Would you share your thoughts to keep work party pages as it is, intact the pyWorkPage or way to exclude this merging step.