SR-123663 · Issue 184330
Multi-cell paste supported for Excel Map Value edits
Resolved in Pega Version 7.1.8
When trying to paste multiple rows into a Map Value using the 'Edit in Excel' feature, a runtime error was generated. The root cause was a refactoring code snippet that assumed only one cell for a change / paste, and the logic failed for multi-cell paste. The property used in the original logic becomes nonexistent (Target.Value) when multiple cells are being pasted. To resolve this, a different property (an array called Target.Value2 ) has been incorporated to populate and adjust the target cells.
SR-123678 · Issue 185155
Resolved issue with duplicate thread creation
Resolved in Pega Version 7.1.8
In Designer Studio, a new thread was created on every click of New Item in the recent list. This was due to the contentID generated not being passed at the document launch time, and the APIs have been updated.
SR-123681 · Issue 187957
AddTime calendar function corrected for calculating expiry times
Resolved in Pega Version 7.1.8
Using the out-of-the-box @addTime function to calculate expiry time was not calculating the correct time or was reporting a missing calendar when passed a calendar instance. The root cause of this problem was due to the calendar instance not using the time zone field while acquiring Gregorian Calendar in the class CalendarUtility. java. This datetime problem has been fixed.
SR-123741 · Issue 186119
Collapsible header text updated for accessibility
Resolved in Pega Version 7.1.8
When a UI layout/section used a collapsible header, JAWS read the field values "Click to expand" and "Click to collapse." Using the word "Click" is not optimal for accessibility, and this field has been changed to "Disclose contents" and "Hide contents."
SR-123750 · Issue 189489
Smoothed multiple portal tabs handling
Resolved in Pega Version 7.1.8
After opening the Case Manager developer portal, if a user portal was opened in a second tab using the 'Switch Portal' option shown in operator menu, returning to the developer portal tab caused that tab to be refreshed and the user portal tab to close. Previously, attempting to open a second portal session in a tab of the same window resulted in a 'Multiple sessions running' error. This limitation was removed in Pega 7.x. However, in this case the 'ShowDesktop' activity could not determine the 'ThreadName' parameter and defaulted to the 'Standard' thread and this change caused the refresh. The logic for determining the thread name has been updated to remove this issue.
SR-123785 · Issue 184291
"Required" checkboxes now working properly with Firefox
Resolved in Pega Version 7.1.8
When using Firefox, putting focus on a field which has "Required" checkbox checked and clicking "Enter" button caused the flow to ignore the checkbox and move forward without showing any error on the screen. This was an issue with the browser not supporting the event prevention code, and the system has been updated to ensure expected behavior.
SR-123815 · Issue 188298
AddTime calendar function corrected for calculating expiry times
Resolved in Pega Version 7.1.8
Using the out-of-the-box @addTime function to calculate expiry time was not calculating the correct time or was reporting a missing calendar when passed a calendar instance. The root cause of this problem was due to the calendar instance not using the time zone field while acquiring Gregorian Calendar in the class CalendarUtility. java. This datetime problem has been fixed.
SR-123847 · Issue 187828
Ensured Property-Set of embedded page list to data page
Resolved in Pega Version 7.1.8
When performing a Property-Set to copy a source Pagelist property into a destination Pagelist property that references an editable data page, the data was not being propagated from the destination Pagelist property into the editable data page. The system has bene updated to ensure the Property-Set step moves the data to the target clipboard page and also updates the editable data page.
SR-123851 · Issue 184413
Stale thread issue resolved and logging updated
Resolved in Pega Version 7.1.8
The error "com.pega.pegarules.pub.context.StaleThreadError: Thread has been recycled" was appearing sporadically in the log files. The root cause was traced to the usage daemon, and has been resolved by changing the logic such that while capturing usage data, the system will avoid setting the last thread as processing thread while taking requestor lock. This avoids usage of a stale thread. Additionally, a change was made to avoid repeated logging of a stale thread error while creating a PRException object when exception occurs do occur due to a stale thread.
SR-123930 · Issue 185707
Corrected Oracle SQLs for checkout/locking
Resolved in Pega Version 7.1.8
Checked Out Specification Rules were not showing as Checked Out on the RuleSet Version. This caused issues when the RuleSet Version was locked based on the assumption that there are no checked out rules. If there was a checked out specification rule, the operator who was working on it could no longer save their changes because the RuleSet Version was locked. This was traced to Oracle not transferring the correct rules column for locking status, and has been resolved with updated triggers for Oracle for both standard and multitenant installs. Contact Pegasystems Global Customer Support for the updated SQL files.