Incomplete XML parsing of Page List properties
When parsing XML that contains several page lists of the same name, only the properties of the first page in the XML are mapped.
For example:
I have a company with this hierarchical structure:
- Boss
- Manager A
- Employee 1
- Employee 2
- Manager B
- Employee 3
- Manager A
In Pega this can be mapped with the class Data-UIGallery-RepeatingLayouts-EmployeeDetails.
The Parse XML tree:
The XML:
When parsing XML that contains several page lists of the same name, only the properties of the first page in the XML are mapped.
For example:
I have a company with this hierarchical structure:
- Boss
- Manager A
- Employee 1
- Employee 2
- Manager B
- Employee 3
- Manager A
In Pega this can be mapped with the class Data-UIGallery-RepeatingLayouts-EmployeeDetails.
The Parse XML tree:
The XML:
<pyEmployeePL>
<pyName>Boss</pyName>
<pyEmployeePL>
<pyName>Manager A</pyName>
<pyEmployeePL>
<pyName>Employee 1</pyName>
</pyEmployeePL>
<pyEmployeePL>
<pyName>Employee 2</pyName>
</pyEmployeePL>
</pyEmployeePL>
<pyEmployeePL>
<pyName>Manager B</pyName>
<pyEmployeePL>
<pyName>Employee 3</pyName>
</pyEmployeePL>
</pyEmployeePL>
</pyEmployeePL>
When running the parse rule with this input, the output is:
The names (.pyName) of Employee 2, Manager B and Employee 3 are not parsed, so the resulting page list is incomplete.
How can this be fixed?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Atos
NL
The answer from Pega Support that solved my issue:
There were earlier known issues with the v7 XML assembler and most of these were addressed natively in 7.2.1 - there aren't any known issues or hotfixes affecting 7.2.1 - see Resolved issue 176925:
https://community.pega.com/node/162781
Can you tell us how you have the 'switchtooldassembler' component?
The DSS entry SwitchToOldAssembler can be set to true to use 6.3 assembler.
Owning Ruleset: Pega-IntegrationEngine
Setting Purpose: SwitchToOldAssemblerThe Old assembler is more stable than new assembler and we do not need to perform regression testing after making this change. So, switching to old assembler should work without any issues. The new parse assembler has many issues and it does not support parsing of more than 2 levels.
There is plan to replace/re-code the new assembler completely in future. The discussions are currently on going in this regard. Moreover, there is also BUG logged already in our system related to the reported issue.
Ideally the behavior of Old assembler should be same as new assembler. It is recommended to use the below Dynamic System Setting entry to resolve the issue:
Purpose : SwitchToOldAssembler
Owning Ruleset : Pega-IntegrationEngine
Value : true
Accepted Solution
Atos
NL
The answer from Pega Support that solved my issue:
There were earlier known issues with the v7 XML assembler and most of these were addressed natively in 7.2.1 - there aren't any known issues or hotfixes affecting 7.2.1 - see Resolved issue 176925:
https://community.pega.com/node/162781
Can you tell us how you have the 'switchtooldassembler' component?
The DSS entry SwitchToOldAssembler can be set to true to use 6.3 assembler.
Owning Ruleset: Pega-IntegrationEngine
Setting Purpose: SwitchToOldAssemblerThe Old assembler is more stable than new assembler and we do not need to perform regression testing after making this change. So, switching to old assembler should work without any issues. The new parse assembler has many issues and it does not support parsing of more than 2 levels.
There is plan to replace/re-code the new assembler completely in future. The discussions are currently on going in this regard. Moreover, there is also BUG logged already in our system related to the reported issue.
Ideally the behavior of Old assembler should be same as new assembler. It is recommended to use the below Dynamic System Setting entry to resolve the issue:
Purpose : SwitchToOldAssembler
Owning Ruleset : Pega-IntegrationEngine
Value : true
