Soap Service created to generate Work- not working using external SOAP UI client.

I created a SOAP based webservice that invokes the flow to create work Objects.

When I tested the webservice by opening the Service rule in Pega. Specifying  wsdl and input values, the webservice created a Work Object sucessfully without any issues.


Now when i do the same request using a SOAP UI client.  The Work Object is getting created but has flow problems " No routing information was provided for this assignment."

and it is getting assigned to adminsitrator.


I found that in case 1, Pega was using the current user context to create the user, so the created work object was being assigned to the current user.

When I make the webservice call through SOAP UI, no such context exist and hence the PRPC is showing flow problems.


How to fix this.  Any help would be appreciated.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

February 18, 2013 - 12:04am


Simple solution for this problem is that in your flow assigment instead of tocurrent operator give any specific worklist details or workbaset details.

February 20, 2013 - 9:07pm


Thanks for your reply.

I tried the soluttion you suggested. Actually in my starter flow, from the start shape I am calling a subprocess that is actually a screen flow.

Now in the screen flow assignment in the starter flow, I cannot find any place where I can route the assignment to a workbasket.

So what i did , that i opened the screen flow and in its start shape I assigned the flow to  work basket.

But still when i make a  webservice call using SOAP UI , I am facing the same error. 

Is there any other place in the starter flow where i can specify the Routing to Workbasket.


February 21, 2013 - 11:14pm

New Update-

In the above way, the ToWorkList is working , and even allowing through SOAP UI.

The ToWorkBasket is not working. 

August 6, 2013 - 4:51pm

Hi screen flow is meant for worklist routing. I guess,there is no way or router shape for screenflow.




August 23, 2013 - 1:09pm

Try creating a separate custom version of your Starter-Flow that handles the Web Service creation of your work object, work item, or case.  In the Web Service version of your starter flow substitute the original screen flow with a utility shape that executes a custom activity that handles the initialization of the new work object, work item, or case and includes the steps suggested earlier by Kartheepan.  Once the work object, work item, or case has been properly initialized you can then call the other sub-flows that handle the rest of your process.





January 19, 2016 - 2:03pm

Hi am not,able to invoke soap service through soap ui getting login cgi issue please suggest

January 19, 2016 - 2:03pm

Hi am not,able to invoke soap service through soap ui getting login cgi issue please suggest