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.
SR-A10345 · Issue 221893
Removed unexpected validation from Page-Change-Class
Resolved in Pega Version 7.2.1
Validation errors appeared on the review screen when tracer was enabled if there was non-conforming data in the non-expanded elements. PDN help for the activity method Page-Change-Class specifies that the method does not validate property values, but the generated java ends up calling DictionaryImpl.validate() and validates the step page without expanding it. Any invalid data in the non-expanded properties would be ignored. However, activating the tracer expands the page and as a result Page-Change-Class attempts to validate all the properties in the page, resulting in errors appearing when appropriate. In order to handle this scenario, validation has been removed from Page-Change-Class method in order to bring the results into line with the help documentation, and if validation is needed it must be added explicitly.
SR-A11437 · Issue 225251
Improve page sync and locking to avoid ConcurrentModifiedException
Resolved in Pega Version 7.2.1
There was a possibility that data page could be modified simultaneously and generate a ConcurrentModificationException, for example where a background thread is expanding a page to check messages at the same time a user thread is expanding the page to fire declaratives on read-only data page before marking it read only. This has been resolved by synchronizing access to a data page instance whenever there is an attempt to expand it from boundaries of data pages code.
SR-A12319 · Issue 226251
Repaired code generation for Single Page property reference
Resolved in Pega Version 7.2.1
Referencing a Single Page property in a Rule-Utility-Function parameter of type ClipboardPage generated Java that created a Clipboard Property at runtime, resulting in a ClassCastException. The code generation process for this was incorrect, and has been repaired.
SR-A12464 · Issue 225916
Property Reference cache handing modified
Resolved in Pega Version 7.2.1
An issue with the property reference cache growing irrespective of the Cache Pruning threshold was traced to the omission of logic to handle references accessed via entry handles. This logic has been added. In addition, PropertyReferencePoolImpl has been modified with a new prconfig setting "cache/propertyreferencepool/enable" which defaults to true. This can be explicitly set to false to disable the pool.
SR-A12485 · Issue 227341
Improved validation error reporting for duplicate radio buttons
Resolved in Pega Version 7.2.1
The label of the radio buttons which contained a required field were not turning red when a validation error occurred if there were multiple radio buttons in the section configured with the same property name. Even though the other radio buttons were hidden by a visible 'when' condition, the label error was applied to the first instance of the radio button which contained the same name. To resolve this, the rule 'pega_validators.js' has been changed to check for duplicate radio buttons and identify the closest label to the field in the label.
SR-A13187 · Issue 229142
JSON mapping performance enhanced
Resolved in Pega Version 7.2.1
JSON mapping performance has been enhanced with the addition of a native JSON property cache along with the introduction of a DSS to skip all unnecessary intensive checks if the JSON node name is found to be valid. This will be handled through a DSS JSON/useNativeAPI which when set uses adoptJSONObject/adoptJSONArray() as the API for inbound JSON parsing. Please note that if the DSS is set, homogeneous arrays are only supported with valuelist configuration in connectors. Heterogeneous arrays are not supported when DSS is set.
SR-A13464 · Issue 227723
Tracer updated to handle encrypted URLs
Resolved in Pega Version 7.2.1
Tracer was not working properly when encrypting URLs. To resolve this, the URL will be obtained from the clipboard property instead of depending on the URL when encryption is present.