Connector and Metadata wizard generated rules
I have used the the Connector and Metadata wizard to generate the integration data model and XML stream and parse rules.
A subset of the generated classes and rules are now relevant for a different integration.
Every complexType definition in the xsd created a corresponding class.
In some of the classes there are "pyAnyName pyAnyNS" stream and parse rules while others don't have these rules.
What are the reasons for the wizard to create these rules for some classes and not to create if for others?
Virtusa IT Consulting
AE
This behaviour is expected, to understand this you need to know use of complex types and substitution groups in xml data mapping, please go through XML data mapping->Extensions restrictions and substitution groups lesson from CLSA part 1 course
Infosys
US
Hello baigh,
thank you for the answer! I do understand how type substitution works, but this does not apply here.
Our schema does not support polymorphism. None of our comlexTypes are extensions of other complexTypes.
In the generated parse rules, which are calling the pyAnyNS pyAnyName those nodes have the subsition setting to "None".
Are there other reasons for Pega to generate the pyAnyNS pyAnyName rules in the classes generated by the wizard?
E.g. would Pega create those rules in order to avoid having a very deep structure in a single rule? I haven't seen a generated structure more than 5 elements below the root in a single (generated) rule. Whenever the tree get's deeper Pega uses Apply rule pyAnyNS pyAnyName.
Is that a coincidence or is there a threshold for the generated rules?
Virtusa IT Consulting
AE
Hello John,
For your first query, I think yes, it tries to avoid the a very deep structure. I am not sure about the second query you have stated above.