Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Request and Response in service "Type" appends differently




In the WSDL, generated in Pega 7.1.6, for any Request and Response, PRPC appends "Type" by default. But in Pega 7.1.8 it appends as "type". Integration with other systems fails due to this.

Steps to Reproduce

1. Create a Request and Response mapping in any Service Rule.
2. Navigate to service package and deploy this method. Generate WSDL.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. This is a side-effect of refactoring performed on WSDL generation in Pega 7.1.7.


This issue is fixed in Pega 7.1.9. As a local-change, modify the WSDL generated to include "Type" instead of "type".

Published August 13, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us