SR-123623 · Issue 184847
Added clipboard clearing for correspondence
Resolved in Pega Version 7.1.8
External assignment was sending out the email correspondence that was configured in earlier stages/flows instead of sending the correspondence that is given in the external assignments rule form. This was a problem with the clipboard where CorrPage was not cleared after the CorrCreate is invoked. To resolve this, CorrNew activity has been modified to add a step to clear the CorrPage.
SR-123628 · Issue 184174
Control inserted for determining Elastic Search (ES) index building
Resolved in Pega Version 7.1.8
As Elastic Search (ES) indexing can take significant time and may cause a temporary performance problem, an enhancement has been added to control whether or not indexes are built during an upgrade. The option also exists to start the build at a later time if it is not performed during upgrade.
SR-123636 · Issue 184161
Trojan horse protection auto-enabled
Resolved in Pega Version 7.1.8
The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.
SR-123636 · Issue 181701
Trojan horse protection auto-enabled
Resolved in Pega Version 7.1.8
The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.
SR-123642 · Issue 187841
Resolved MultiSelectList control issues for Microsoft Internet Explorer 9+
Resolved in Pega Version 7.1.8
The MultiSelectList control was no longer working for Microsoft Internet Explorer 9+. When a user attempted to select one or multiple items in the MultiSelectList control, the values were not captured when going to the next screen and a JavaScript exception was thrown. This was due to an API change in newer versions of the Internet Explorer (Microsoft Internet Explorer) browser. Microsoft Internet Explorer is following a more strict standard about how the createElement function is used, which caused the JS error to be thrown, and the system has been updated to resolve this issue.
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-123686 · Issue 184976
Properly resolved HTML tags in ListView
Resolved in Pega Version 7.1.8
If any HTML tags such as were used inside the Full Description of ListView, the tags are were not being resolved and were instead displayed as-is. This was caused by how the XSS filter affected the way the tags were reference when returned to the browser, and has been fixed.
SR-123712 · Issue 184471
Resolved schema qualification for dedicated tables
Resolved in Pega Version 7.1.8
When creating a data table / data class via the wizard, selecting "Create Dedicated Table" would show success on the wizard screen but the class was mapped to "pr_other" and an error was logged. This was caused by incorrect schema qualification for WorkHistory, and has been resolved by inserting a requirement for implicit schema privileges.