SR-C33849 · Issue 375408
Events properly stored in Stream Data Set
Resolved in Pega Version 8.1
Changes made to the Stream commit log storage structure in a previous fix resulted in unintended loss of the events information. This has been corrected by updating the Stream commit log directory name.
SR-C3391 · Issue 358482
Excel/Word copy/paste to RTE font resolved
Resolved in Pega Version 8.1
When pasting the content from Excel or Word into RTE, the font of the copied text was retaining the font from Excel/Word instead of changing to the one already present in RTE. This has been fixed by adding the lang attribute to the span element.
SR-C34208 · Issue 373283
Fixed unexpected grid tab key behavior change
Resolved in Pega Version 8.1
After upgrade, tab key events configured on any text input field were not being performed and the browser focus shifted to the next editable element. This was an issue with the Grid eventtype being hardcoded as keyup, and it has been corrected so the eventtype is keydown.
SR-C34388 · Issue 373481
New interface has been exposed to allow custom merge logic for putall
Resolved in Pega Version 8.1
While removing an item from a pagelist within a work object in the client cache, pagelist.remove(index) is called to complete that process. After syncing to the server, the item unexpectedly returned to the page list. This was traced to the Item removed from PageList in Cache being re-added to PageList because 'putall' was not supported with this configuration. To resolve the issue, a new interface has been exposed to allow custom merge logic for putall.
SR-C34516 · Issue 388567
Dynamic layout for pxDiscoverableItemsCount split to better handle individual 'when' conditions
Resolved in Pega Version 8.1
After upgrade, each report definition was showing a huge space under the filter section when using dynamic layout in the pxDiscoverableItemsCount section. If the layout format was changed from inline to any other layout format, the space did not appear. This was an issue with the custom styling for the Inline format that led to the Discovery item in reports taking up space even though it was hidden. This has been resolved by breaking the dynamic layout into two dynamic layouts so the 'when' condition could be on the individual dynamic layouts. If nothing is displayed within it, the dynamic layout markup won't be included.
SR-C34567 · Issue 375117
MSOParseExcelFile skips cell formula for Page List value
Resolved in Pega Version 8.1
MSOParseExcelFile was reading the formula along with the data when mapping to page list values. In order to ensure only the cell content is mapped and not the formula, parse will skip if the nodename is of type formula.
SR-C34597 · Issue 375837
ShowLogoffTimer displays properly in Microsoft Internet Explorer
Resolved in Pega Version 8.1
The Log off time out warning pop-up was not displaying properly in Microsoft Internet Explorer and showed an unexpected scroll bar. This was due to legacy table-based markup structure that is no longer supported by Microsoft Internet Explorer , and it has been removed from ShowLogoffTimer.
SR-C34654 · Issue 374524
XSD files sent to the correct shared path
Resolved in Pega Version 8.1
XSD files were not sent to correct shared path. This was traced to the creation of the zip file missing XSD when getAllProperties is true, and has been fixed by adding logic to not skip the XSD when generateXSDForGetAllProperties DSS is enabled.
SR-C35027 · Issue 377314
Subject field of file attachment expanded to 96 characters
Resolved in Pega Version 8.1
Previously, the description text (Subject field) of a file attachment was limited to 64 characters. In order to support longer fields, the truncation at 64 characters has been removed, the property-set pyNote has been moved to Step 11, and the attachment name will be validated Database pyMemo column size (96 characters) and truncated if the length is more than db memo size.
SR-C35036 · Issue 374126
AttachmentCategoriesToSend in CorrNew fixed
Resolved in Pega Version 8.1
When calling CorrNew and passing a value to "AttachmentCategoriesToSend", the attachments in the provided category were not added to the email being sent. This was caused by a step-order error introduced when the activity was refactored, and has been corrected.