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-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-A2361 · Issue 214536
XSS fix updated for IAC with CSRF tokens
Resolved in Pega Version 7.2
After updating to address a potential XSS security issue, some problems were found with using IAC with CSRF tokens in the pathinfo. Additional checks have been added to handle this scenario.
SR-A7487 · Issue 221274
Better Japanese font handling in CreatePDF smart shape
Resolved in Pega Version 7.2
The CreatePDF smart shape was not able to properly parse Japanese font characters in section data. This has been corrected by changing the default font to 'MS PGothic' which better supports Japanese.
INC-194330 · Issue 708711
Added special character handling for DecisionTable column-label
Resolved in Pega Version 8.7.2
The label of a decision-table column was being appended to the original decision-table return-value. The column label and comparator were handled differently for columns containing special characters (+, -, *,...), causing the data after the special character to be trimmed and appended to the row output value. This has been resolved by adding handling for special characters so the output and the label are rendered properly.
INC-200802 · Issue 714845
Line break handling added for setting required question asterisk
Resolved in Pega Version 8.7.2
If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.
INC-205666 · Issue 702936
Database table correctly prevents deletion if there are descendant classes
Resolved in Pega Version 8.7.2
When deleting a concrete class with descendant classes via an activity (Rule-.Delete), the Rule-Obj-Class.ValidateDeleteInternal activity was throwing an error message indicating the class could not be deleted due to descendant classes. However, the corresponding database table rule was deleted anyway. Investigation showed this was caused by ValidateDeleteInternal not reaching the Obj-Save-Cancel step. This can be fixed by modifying step 11, the post when conditions, to jump to END and set the END label at the Obj-Save-Cancel step instead Exit-Activity, but this issues has been resolved by updating all failure states to run end step. In addition, security has been updated to disallow "Allow invocation from browser".