SR-B32618 · Issue 276417
Enhancement added to maintain blank properties when using History Snapshots
Resolved in Pega Version 7.3
In HistorySaver, using ClipboardProperty.setValue to save snapshot data for the previous version of the rule had the side effect of stripping blank properties from the clipboard page, and so any rules that rely on these properties would not be restored correctly. To resolve this, an enhancement has been added to specially handle instances History- class and its descendants to serialize blob with EmptyProperties.
SR-B32618 · Issue 276417
Enhancement added to maintain blank properties when using History Snapshots
Resolved in Pega Version 7.3
In HistorySaver, using ClipboardProperty.setValue to save snapshot data for the previous version of the rule had the side effect of stripping blank properties from the clipboard page, and so any rules that rely on these properties would not be restored correctly. To resolve this, an enhancement has been added to specially handle instances History- class and its descendants to serialize blob with EmptyProperties.
SR-B3263 · Issue 275060
Performance improvements for opening pop up grid dialog box
Resolved in Pega Version 7.3
Performance improvements have been made in opening the pop up dialog box in pzPerformGridAction by executing the copying logic only if the page is read-only.
SR-B3280 · Issue 279492
Resolved skimming error
Resolved in Pega Version 7.3
Errors were getting thrown on the screen while performing minor ruleset version skimming of one version into a new ruleset version which was higher than the ruleset version mentioned in the application rule. This was due to the target version not having the correct context because the application didn't yet exist or because the operator was not logged into the target context. In order to resolve this, the messages in the page will be cleared before skimming to avoid validation. It is then recommended to log into the new application and use the Application Validation tool to validate the newly created rulesets application.
SR-B32965 · Issue 294552
Agent minimum wakeup time changed to 1 second
Resolved in Pega Version 7.3
In order to allow sites to better customize agent schedules for picking up segments, the agent minimum wakeup time has been changed from 5 seconds to 1 second.
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-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 283868
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-B34135 · Issue 291962
Existing Org Names used in new layer
Resolved in Pega Version 7.3
In the Advanced configuration section, existing Organization Names were not being used while creating a new framework on top of an existing framework/application. This was an issue with the framework ruleset prerequisite preparation logic incorrectly setting the ruleset version for the dependency of the framework integration ruleset, and has been fixed.