You said you deselected the pyWorkParty property from the parameters? If you do not need to set the pyWorkParty, you should remove the pyCaseManagementDefault WorkParty rule specified in the Process tab instead.
When I am selecting the input properties for the service I have deselected the .pyWorkParty().pyTemplateInputBox and .pyPartyClassPrompt as I do not want these properties set. During the first step the case is assigned to a work basket. When running the service in the new version I recieve the error even when .pyWorkParty().pyTemplateInputBox is not included as one of the parameters for the service.
In 7.1.7 I could use the service without setting these properties.
When you create the case manually it calls createworkpage under which it creates newPartypage activity which looks for current operator available in the clipboard i.e. pxRequestor page Data-Party.CurrentOperator activity which sets .pyWorkPartyUri value.
In the context of the service rule running pxRequestor page is un-available and could not able to set pyWorkPartyUri value. you can try to set in your flow before first assignment set this value.
PRPC's Online Help does not search for sentences (as it strips single quotes and fails on double quotes) and thus limited to separate keywords even dropping words like "on". However, in the result list for Visible on Entry is found a page on configuring Work Parties stating:
"VOE? Select the VOE (Visible on Entry) checkbox to cause the PartyDisplay HTML for this party to appear at runtime at the time of the first display of the work item entry form, rather than only after a user makes a choice from a selection box."
Sounds more like a convenience setting, but let me try to Run a simulation of the Service SOAP rule after having VOE set to false...
The context of the very same pyErrorMessage is due to some invalid Response structure and not the Request XML you are sending to the service (using the simulator). Am I right?
I read that the Service Wizard pre-selects the required properties for the service to function. So I conclude, simply de-selecting those is not a real solution to the above problem. Sadly, I cannot understand the explanation written by raghu.raob.
Actually I'm not sure what Flow Type I'm supposed to select as part of the SSA exercise for building a SOAP service. On the Service SOAP rule I found "StandardBasicWork". Is that correct and what is the meaning of this Flow Type?
Since this exercise I'm confused about the difference of Flow, Flow Action and this Flow Type.
More fundamentally, I'd like to know where to look in the documentation to read about each of the available standard flow types when using the Service Wizard aka Service Accelerator. Does anyone know?