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

Parse XML mapping property to blank value

SA-502

Summary



XSD schema wizard does not work with certain element definition. 

XSD accelerator generated the rule definition for below PolicyNumber element but there is a runtime issue. On executing the generated Parse Rule, it does not map the value for the element PolicyNumber to clipboard property PolicyNumber. 

<xsd:element name="PolicyNumber" type="C-25"/> 
<xsd:complexType name="C-25"> 
<xsd:simpleContent> 
<xsd:extension base="C-25_NoID"> 
<xsd:attribute name="id" type="ID"/> 
</xsd:extension> 
</xsd:simpleContent> 
</xsd:complexType> 
<xsd:simpleType name="C-25_NoID"> 
<xsd:restriction base="xsd:string"> 
<xsd:maxLength value="25"/> 
<xsd:minLength value="1"/> 
</xsd:restriction> 
</xsd:simpleType> 

Sample XML data:
<?xml version="1.0"?>
<Policy id='a' xmlns:a="http://my_server/standards/xml/">
    <a:PolicyNumber id='b'>123</a:PolicyNumber>
</Policy>



Error Messages



Not Applicable


Steps to Reproduce



1. Import the PolicyNumber XSD using Pega Accelerator. 
2. Check the generated Parse Rule for PolicyNumber element. 
3. Open the node 'PolicyNumber'. Notice that there is no value in the Property field.

Root Cause



This is an issue with Pegasystems' code or rules.

Resolution



Perform the following local-change.

1. Open the generated Parse Rule 
2. Edit the PolicyNumber node. 
3. Set '.Value' for Property field under the 'Mapping' tab. 
4. Save the rule.
Suggest Edit

Published November 24, 2015 - 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