SR-C33742 · Issue 373407
AggregationValue object modified to support aggregating records with multiple measurements
Resolved in Pega Version 8.1
VBD Synchronization was failing with the exception "java.lang.IllegalArgumentException: Aggregation failed due to unexpected value type". This occurred when processing a specific sequence of IH Facts on the same day, in which IH Facts without measurements were followed by IH Facts with multiple measurements, such as:1) Fact with dimension values "A,B,C" and without measurements 2) Fact with dimension values "D,E,F" and with multiple measurements (must be multiple) 3) Fact with dimension values "A,B,C" and with any of the measurements from 2. To resolve this, the tracking of field count in each aggregate has been updated to handle multiple added measurements.
SR-C33761 · Issue 376121
pyFileSize changed to type Text
Resolved in Pega Version 8.1
An error occurred when using an RD to fetch pyFileSize of all attachments uploaded from Pulse. This was traced to a type mis-match: while the property itself is a decimal, the activity was setting a string value with alphanumerals. To avoid this error, the pyFileSize property will be created with type as Text.
SR-C33768 · Issue 378863
Fixed ESRI maps offline case causing unending sync
Resolved in Pega Version 8.1
The Pega windows app on desktop was showing syncing all the time when logged in online and ESRI Maps was configured through the non-auto generated section on an offline case. This has been corrected.
SR-C33768 · Issue 379381
Fixed ESRI maps offline case causing unending sync
Resolved in Pega Version 8.1
The Pega windows app on desktop was showing syncing all the time when logged in online and ESRI Maps was configured through the non-auto generated section on an offline case. This has been corrected.
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.