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

XSD is getting generated with header and footer elements



Executing an extract rule (manually inside Pega) in Pega 7.2 generates the XSD in a different structure from previous versions. As such, these XSDs cannot be provided or injected into the existing reporting systems that processed the extracted data in previous versions. XSD is getting generated with header and footer elements.

User requires a fix to generate the XSDs without header and footer.

Error Messages

Not Applicable

Steps to Reproduce

1. Create property in the target class and a page list property with the properties in it.
2. Create extract rule as show in the attached document.
3. Test the connectivity.
4. Run extract rule from the UI.
5. Check the generated XSD has header and footer. User is expecting a XSD without header and footer as it happens in PRPC 6.X series.

Root Cause

A defect or configuration issue in the operating environment:


Perform the following local-change:

1. Stop the server.
2. Copy the provided xslt file to the server file system.
3. Open a prconfig.xml file (example C:\tomcat-instances\prpc721\apache-tomcat-8.0.35\webapps\prweb\WEB-INF\classes) and add the below line to it:

<env name="extract/schema/xsl/path" value = "/filesConfig/extract/pytree2schema.xslt" />
Notice that header and footer sections are commented out in this XSLT file.
4. Save the prconfig file.
5. Restart the server, run the extract rule and observe that new generated XSD has no header and footer.

Suggest Edit

Published August 1, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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