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
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?
Posted: 5 years ago
Posted: 11 Apr 2017 10:30 EDT
Habeeb Baig (HabeebBaig)
Technical Solutions Engineer