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-B3279 · Issue 274808
Better handling for empty LockInfo page
Resolved in Pega Version 7.3
Intermittent errors were encountered when attempting to expand rows of a repeat grid. This was due to handling difference related to a pre-condition check for the LockInfo page used to create error messages. Since the LockInfo page is not required or consistently used, the system has been updated to better handle cases where it is empty.
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-B32839 · Issue 292388
Performance improvements for headless decisioning
Resolved in Pega Version 7.3
Performance issues were seen in Service Pega 7.2 related to scaling vertically when used for in a headless decisioning scenario. The code has been refactored to remove redundant calls to requestors in ServiceAPI, HttpService, SOAPUtils and SOAPService as well as additional classes and other classes to correct this.
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-B33088 · Issue 293375
pyGetAttachmentContent modified to access class for new properties
Resolved in Pega Version 7.3
The out-of-the-box properties IsDataPageRefreshed and PxAttachName were generating errors indicating the page contains undefined properties. The issue was with the activity pyGetAttachmentContent. As the properties pxAttachName and pyURL etc. are present in their respective classes and the data page class is Data- the errors were not visible. To correct this, pyGetAttachmentContent has been modified to use Page-Change-Class in the activity to change to the correct class so that properties can be accessed. pzRemoveAttachments and pzRefreshAttachmentList have also been updated to use pyIsDataPageRefreshed (new property created).
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.