SR-A13449 · Issue 226932
Passivation fixed for softphone pages
Resolved in Pega Version 7.2
If a softphone page idled for 4 hours, a requestor level page (ScreenPopControlPort) became empty and prevented the user from logging in again. This was caused by a passivation issue that led to the parent page not being correctly set upon reactivation, and has been fixed.
SR-A13449 · Issue 222715
Passivation fixed for softphone pages
Resolved in Pega Version 7.2
If a softphone page idled for 4 hours, a requestor level page (ScreenPopControlPort) became empty and prevented the user from logging in again. This was caused by a passivation issue that led to the parent page not being correctly set upon reactivation, and has been fixed.
SR-A10527 · Issue 221023
Issue with unwanted additional PageList property row corrected
Resolved in Pega Version 7.2
An empty row was being created on a page list property used in a work-item due to a logic issue with the TrackSecurityChangesLogic activity. This has been corrected.
SR-A10527 · Issue 221549
Issue with unwanted additional PageList property row corrected
Resolved in Pega Version 7.2
An empty row was being created on a page list property used in a work-item due to a logic issue with the TrackSecurityChangesLogic activity. This has been corrected.
SR-A5351 · Issue 218740
Optimized Clipboard reference processing
Resolved in Pega Version 7.2
Enhancements have been made to optimize reference properties processing for the ClipboardPageImpl.expandAllIfUnexpandedReferenceProperties method.
SR-A5351 · Issue 216605
Optimized Clipboard reference processing
Resolved in Pega Version 7.2
Enhancements have been made to optimize reference properties processing for the ClipboardPageImpl.expandAllIfUnexpandedReferenceProperties method.
SR-A6621 · Issue 221216
Fixed locking on node level declare pages
Resolved in Pega Version 7.2
In a scenario where data is being loaded from external system using an activity, the data page should be loaded only once for the first requester and all following requestors should refer to the loaded data page until it is expired. However, when multiple users accessed the data page simultaneously, the data page was being loaded for each one. This was traced to a timing issue with locking, and ReadOnlyDataPageHandler->loadDataPage() has been updated to insure node level data pages do the 'put' operation before releasing a lock.
SR-A4310 · Issue 212995
Fixed locking on node level declare pages
Resolved in Pega Version 7.2
In a scenario where data is being loaded from external system using an activity, the data page should be loaded only once for the first requester and all following requestors should refer to the loaded data page until it is expired. However, when multiple users accessed the data page simultaneously, the data page was being loaded for each one. This was traced to a timing issue with locking, and ReadOnlyDataPageHandler->loadDataPage() has been updated to insure node level data pages do the 'put' operation before releasing a lock.
SR-A11245 · Issue 222247
Designer Studio query/filter matching improved
Resolved in Pega Version 7.2
The activity to fetch instance lists in Designer Studio uses a query which performs an UPPER() operation against the pzInsKey column of the target rule table, but the Ignorecase option was being used for the pzInskey filter. The filter has been modified to use toUppercase edit input for filter value.
SR-A11637 · Issue 228995
Newlines encoded for CSV import
Resolved in Pega Version 7.2
A new line character within the csv fields was treated incorrectly and parsed as an end of a row in csv during import. To avoid this, the parsing logic has been changed to handle new line characters within the fields.