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".
SR-A11592 · Issue 224578
Application Document wizard encoding updated for accented characters
Resolved in Pega Version 7.2
Accented characters were not displaying properly in documents generated with the Application Document wizard. To correct this, the GenerateDocument function contained in the DocumentApp library has been modified to specify the character encoding.
SR-A13378 · Issue 229039
Check added for keystore file name separators
Resolved in Pega Version 7.2
When uploading a keystore file from a Windows client to a Linux system, the result did not have the fileName correctly extracted from the path due to the difference in file separators ("/" vs "\\"). A check has been added for proper handling.
SR-A5244 · Issue 221002
Fixed compatibility issue with Application Document Wizard
Resolved in Pega Version 7.2
A bug in the open source JAR used to generate sever-side documents in the Application Document Wizard caused corrupted documents that were not able to be imported into Word 2010. The corrected JAR has now been obtained from the external team and repackaged into the system.
SR-A5244 · Issue 220453
Fixed compatibility issue with Application Document Wizard
Resolved in Pega Version 7.2
A bug in the open source JAR used to generate sever-side documents in the Application Document Wizard caused corrupted documents that were not able to be imported into Word 2010. The corrected JAR has now been obtained from the external team and repackaged into the system.
SR-A12638 · Issue 223936
Check added to handle mismatched property names given in referred page
Resolved in Pega Version 7.2
If a property name was provided in a list criteria by referring page name, it generated type mis-match error even though the property was of the same type. Creating a new RD with same criteria avoided this error, but a check has been added to "Validate_Report_Condition" to determine whether the property is a leaf or page property . If it is a page property, the system will prefix that property with a "." to resolve the mis-match issue.
SR-A7008 · Issue 216642
Number separators localized for Excel export handling
Resolved in Pega Version 7.2
While using the Export to Excel button in reports, some of the figures in numbers columns displayed warning messages indicating they were formatted as text. This was a localization issue where numbers containing unusual separators were interpreted as strings, and has been resolved with a code change that allows Excel to decide the right format based on locale.