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

Stream Name and XML Type fields in User Data form are read only

SA-20459

Summary



After importing a WSDL, user noticed that the Stream Name and XML Type fields present in User Data form of a node element in XML Stream Rule are not editable.

The Stream Name and XML Type fields are populated with generic names like pyAnyNS and pyAnyName respectively.
User wants to know if the XML Stream Rule in Pega 7.1.8 is broken because in PRPC 6, finds that all the node elements has editable fields with appropriate values.


Error Messages



Not Applicable.


Steps to Reproduce

  1. Import the WSDL file.
  2. The XML Stream rules will have node elements in the tree structure. 
  3. Click on a node element to open the User Data form for that element.
  4. The "Stream Name" and "XML Type" fields present in User Data form for the corresponding node element of the XML Stream Rule are displayed as read only fields.


Root Cause



The reported behavior is not an issue. The feature is working per design of XML Stream Rule in Pega 7.1.8.

Resolution



Here’s the explanation for the reported behavior: 

"Allow tree editing?" option present in Mapping tab of a XML Stream Rule must be checked to enable editing option for "Stream Name" and "XML Type" fields present in User Data form for a node element.

This will also enable the icon to allow us open the XML Stream Rule referenced in "XML Type" field.
​The referenced XML Stream Rule has the embedded elements.
Suggest Edit

Published March 4, 2016 - 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