SR-A11445 · Issue 222408
Wildcard extraction trims extraneous spaces from BIX output
Resolved in Pega Version 7.2
An extra space was being appended to the XML output file name when %t was used. The ExtractImpl.replaceWildCards() method has been updated to trim any additional spaces at the end.
SR-A12684 · Issue 224534
Extracts count corrected when using XML as output
Resolved in Pega Version 7.2
While running an extract using XML as output, a difference was observed in the number of records being extracted when compared with 'Database Schema' as output. The Pega-BIX logs contained failed records with 'Index out of bounds' exceptions. This was traced to missing handling for the value group property references in this scenario, and has been corrected.
SR-A10974 · Issue 223153
BIX Manifest enhanced to include fully qualified property names
Resolved in Pega Version 7.2
If an page list property with the same name existed under two levels in the extracted data (specified in the extract rule multiple times), there was no way to differentiate them when viewing the BIX Manifest file. To resolve this, an enhancement has been added to ExtractImpl to include the fully qualified name for the property.
SR-A12324 · Issue 226656
XML manifest output support added for nodes with 'px' naming schemes
Resolved in Pega Version 7.2
When the 'pxSkillsRequired' value Group property was part of the properties being extracted, node names starting with px generated an exception while writing to XML manifest output format. Handling has now been added to support node names starting with 'px'.
SR-A9893 · Issue 220141
Checkbox values retained in Hybrid client on iOS
Resolved in Pega Version 7.2
Checkbox property values were not retained in Hybrid client on iOS inside a repeating dynamic layout, displaying the checkboxes as unchecked even when the property associated with the checkbox had value = true. This was not an issue when running the application on a desktop or in a regular mobile browser. This was traced to the ID attribute value of all the checkboxes being rendered as the same in this circumstance, and the system has been updated to generate unique ID attributes if bOptimized is true in the pzGenerateCheckbox RUF.
SR-A14732 · Issue 228331
pxObjClass correctly applied to nodes for extract rule form
Resolved in Pega Version 7.2
If pxObjClass was selected for the top level node in the extract rule form, BIX would use use pxObjClass for all of the embedded nodes irrespective of whether pxObjClass was selected for the embedded node or not. If pxObjClass was not selected in the top level node but then selected for all of the embedded nodes, then the system would not use pxObjClass for any of the nodes. To correct this, changes have been made to ExtractImpl and BIXXMLStream so that pxObjClass will be added to those nodes for which pxObjClass property has been explicitly selected in the extract rule form.
SR-A15173 · Issue 229236
pxObjClass correctly applied to nodes for extract rule form
Resolved in Pega Version 7.2
If pxObjClass was selected for the top level node in the extract rule form, BIX would use use pxObjClass for all of the embedded nodes irrespective of whether pxObjClass was selected for the embedded node or not. If pxObjClass was not selected in the top level node but then selected for all of the embedded nodes, then the system would not use pxObjClass for any of the nodes. To correct this, changes have been made to ExtractImpl and BIXXMLStream so that pxObjClass will be added to those nodes for which pxObjClass property has been explicitly selected in the extract rule form.
SR-A3380 · Issue 213940
FlindAllReferencingRules updated to handle blocked rules
Resolved in Pega Version 7.2
If a rule being referred to was blocked, findAllReferencingRules() generated an NPE and document generation did not show ERDs. The code has been updated such that if a referenced rule is blocked, the interaction will continue to the next rule.
SR-A7173 · Issue 220154
Generated ERD diagrams compatible with Visio 2013
Resolved in Pega Version 7.2
ERD diagrams opened in Visio 2013 were jumbled and generated an error when opening the vdx file: "This UML Model Diagram was created with a feature that is not supported in this version of Visio." This has been fixed.
SR-A10195 · Issue 222272
Guardrail warning justifications remain after label change
Resolved in Pega Version 7.2
When an activity rule had a justification on certain types of guardrail warnings and the rule was modified such that one of the warnings goes away, then the other justifications disappeared but the guardrail warnings remained. This was due to the Rule-StandardValidate activity removing the existing warnings if the label was changed, and the 'when' condition has been updated to remove warnings only when the label is changed and the operation is not "Save".