Starting cases via Service
I am using Pega 7.1.8
I created a Service to call pyStartCase and deselected the pyWorkParty property from the paramaters. When the Service is called I get the error:
<pyMessages>
<pyErrorCount>1</pyErrorCount>
<pyErrorMessage>.pyWorkParty(Owner).pyWorkPartyUri: This field may not be blank </pyErrorMessage>
<pyPageName>pyWorkPage</pyPageName>
</pyMessages>
When Using Pega 7.1.7 this was not an issue and I could call the Service without setting the pyWorkParty.
Pegasystems Inc.
SG
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.
Fusion Technology
US
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.
Fusion Technology
US
I also removed the WorkParty rule and I received the same error.
Pegasystems Inc.
SG
I created a new Case type to test this out in Pega 7.1.8. Simple flow to send an email.
After running the Service Wizard and unchecking the .pyWorkParty().pyTemplateInputBox and all other properties, I simply enabled a new work to be created.
I ran the Service and it worked fine. Perhaps you will like to create another Service rule using the wizard and try again?
Fusion Technology
US
I have created a new service and experienced the same problem. I opened up a Support Request and was told that the field is now a required field.
Pegasystems Inc.
SG
Well that is interesting...
Fusion Technology
US
Agreed. I am not apposed to using the .pyWorkParty().pyTemplateInputBox property I just cannot find an example of how to use this field.
Any idea of what this field is expecting?
Pegasystems Inc.
SG
Not too sure myself. Put in a dummy value and see where it shows up?
Fusion Technology
US
I have attempted to put in a username or workbasket and still receive an error. When looking at the clip board I don't see a property called pyTemplateInputBox.
IPA
AU
Hi James,
Have you tried setting .pyWorkParty(Owner).pyWorkPartyUri with some dummy value?
Are you using create harness for the case?
Vamshi
Fusion Technology
US
Yes I have. I have tried many things.
When I attempt to populate the field I get two seperate errors:
<pyErrorCount>2</pyErrorCount>
<pyErrorMessage>.pyWorkParty(Owner).pyWorkPartyUri: This field may not be blank.</pyErrorMessage>
<pyErrorMessage>.pyWorkParty(pyWorkParty1).pyWorkPartyUri: This field may not be blank.</pyErrorMessage>
<pyPageName>pyWorkPage</pyPageName>
I am using the pyStartCase Flow Action to start the case.
IPA
AU
Hi JamesK69,
Could you see on your Flow rule form --> Process tab, if the option Skip create Harness is checked or unchecked
Vamshi
Fusion Technology
US
It is checked. I also tried with it unchecked with no success.
IPA
AU
Sorry for asking you another question, have you tried running the flow / case manually?
What happens, will it ask you to enter pyWorkParty details or same error is thrown?
Vamshi
Fusion Technology
US
If I start the case manually, I do not receive any errors.
Virtusa Corp.
US
Hi James,
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.
Pegasystems Inc.
IN
disabling visible on entry for work party owner helps?
SynTouch
NL
Could anyone point me the the location where I could set this Visible On Entry (VOE) property for some pyWorkParty, i.e. Employee or even Owner? What is this supposed to control?
I did located "pyPartyRoleVisibleOnEntry" on the Clipboard already, but like to know the proper location for a permanent change from "true" to "false" and tests if this amounts to anything.
How this would impact functioning of a SOAP Service (Run) is still unclear.
SynTouch
NL
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...
SynTouch
NL
Where do I find this Work Parties form holding the Valid Parties tab as mentioned on the following help page?
PS. No breadcrumbs nor sync to the Content/Index pane?
Fusion Technology
US
Thank you Phani. That fixed the issue.
SynTouch
NL
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?