SR-B33827 · Issue 292793
XSS filter added to pxTextAbridge to correct stray characters
Resolved in Pega Version 7.3
pxTextAbridge was not working properly. If the "> characters were used, e.g., Sample Text "> Test, this will be displayed as " Test">Sample Text "> Test". This was caused by text that was passed to pxTextAbridge control's property getting incorrectly to the title attribute, and has been resolved with the addition of a cross scripting filter for title and property value.
SR-B33919 · Issue 291326
NexFlow requestor performance improvements
Resolved in Pega Version 7.3
The deployment of the Nexflow Application RAP was failing due to a requestor synch timeout if 'includeSynonyms' was enabled on the DB connection. Code updates have been implemented to improve performance to resolve this.
SR-B33962 · Issue 291929
Overview rendering enhanced for multiple subcases
Resolved in Pega Version 7.3
When a case was created with two subcases, assignment of one of the subcases was not getting rendered in the overview section. This was caused by the pzLoadNestedCasesForClass checking contains on pyID and has been resolved by changing the function to check on pzInsKey. Also in step 5.4, the appending of pyID has been changed to pzInsKey.
SR-B33991 · Issue 292845
Corrected ability to hide filters for Export to PDF
Resolved in Pega Version 7.3
The "Display report filters" check-box was not being honored on export to PDF, causing the filters to always be shown. This has been corrected with an added visibility condition to show or hide a filter section based on the value of .pyDisplayReportHeader, and a check has been added in "RRBodyDiv" HTML rule to show header only when pyDisplayReportHeader is true.
SR-B34004 · Issue 292912
New config added for tuning PropertyInfo threads on high-load systems
Resolved in Pega Version 7.3
In order to resolve an issue with blocked threads due to contention while getting PropertyInfo objects from the dictionary during periods of extremely heavy loads, the new config setting "cache/dictionarycache/reduceContentionGetPropInfo" has been introduced. This config will default to false to preserve the current performance functionality; setting it to true will change the behavior to acquire locks on smaller blocks of code instead of bigger blocks to reduce contention.
SR-B34004 · Issue 276857
New config added for tuning PropertyInfo threads on high-load systems
Resolved in Pega Version 7.3
In order to resolve an issue with blocked threads due to contention while getting PropertyInfo objects from the dictionary during periods of extremely heavy loads, the new config setting "cache/dictionarycache/reduceContentionGetPropInfo" has been introduced. This config will default to false to preserve the current performance functionality; setting it to true will change the behavior to acquire locks on smaller blocks of code instead of bigger blocks to reduce contention.
SR-B34026 · Issue 292199
Added check for offline case to avoid unsupported refresh
Resolved in Pega Version 7.3
Refresh other section is not supported in offline case, but was generating a Null Pointer Exception in the logs. This has been fixed by adding a check that will not generate the java code for Data transform for refresh other section in an offline case.
SR-B34134 · Issue 292328
Bulk upload logic improved for SAI contact creation
Resolved in Pega Version 7.3
While bulk uploading a Contact in Sales Automation for Insurance, if the Contact BU template had empty space in the pyID column. the Contact's Individual account and C2A link were not getting created. This was because the bulk upload column needed to be trimmed in the bulk upload process to take the pyID as empty or null, and the logic has been updated to check whether the provided id is empty or not.
SR-B34134 · Issue 292929
Bulk upload logic improved for SAI contact creation
Resolved in Pega Version 7.3
While bulk uploading a Contact in Sales Automation for Insurance, if the Contact BU template had empty space in the pyID column. the Contact's Individual account and C2A link were not getting created. This was because the bulk upload column needed to be trimmed in the bulk upload process to take the pyID as empty or null, and the logic has been updated to check whether the provided id is empty or not.
SR-B34134 · Issue 292787
Bulk upload logic improved for SAI contact creation
Resolved in Pega Version 7.3
While bulk uploading a Contact in Sales Automation for Insurance, if the Contact BU template had empty space in the pyID column. the Contact's Individual account and C2A link were not getting created. This was because the bulk upload column needed to be trimmed in the bulk upload process to take the pyID as empty or null, and the logic has been updated to check whether the provided id is empty or not.