SR-B33262 · Issue 289895
IACAuthentication security improved
Resolved in Pega Version 7.3
The IACAuthentication activity assumed third party authentication and did not check for a password. In order to improve security, default password validation has been added to the shipped IACAuthentication activity.
SR-B33262 · Issue 290338
IACAuthentication security improved
Resolved in Pega Version 7.3
The IACAuthentication activity assumed third party authentication and did not check for a password. In order to improve security, default password validation has been added to the shipped IACAuthentication activity.
SR-B33686 · Issue 295039
Repaired REST Connections with proxy
Resolved in Pega Version 7.3
After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.
SR-B33756 · Issue 295710
Updated logic check for property panel invalid actions
Resolved in Pega Version 7.3
Configuring invalid actions on the events & actions property panel was not triggering the validation messages when submitted, saved, and checked-in. When the action was re-opened, no changes were saved. This was due to a segment of code called on load of the property panel that remained for backwards compatibility but should not have been called in this scenario. This has been fixed by adding a check at the top of this activity for messages/errors which will route the logic appropriately.
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-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-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.