Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

WSDL generation for Service SOAP rules

Updated on November 23, 2022

After you have created all the Service SOAP rules that are to be included in a service package, generate WSDL files that describe the services in the package. Then, you can copy the generated WSDL files to the system on which you are developing the SOAP client and use it to create your SOAP client application.

Open the service package data instance to create a WSDL file. You can copy this file to the client (calling) system to support deployment. For more information, see Service Package form - Completing the Context tab.

Note: Although SOAP services support the nillable attribute, the WSDL file that Pega Platform generates does not include any nillable attributes. If required, edit the WSDL file to include an attribute similar to the following:
<xsd:elementname="shipDate" type="xsd:date" nillable="true" />

Pega Platform can process a SOAP message that contains:

<shipDate xsi:nil="true"></shipDate>
  • Previous topic Service SOAP form - Working with the Test Cases tab
  • Next topic Modifying character set encoding for Service SOAP rules

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us