SR-C36692 · Issue 377206
Corrected double-encoding of Japanese characters in My Team name
Resolved in Pega Version 8.1
Creating a team from the case default portal (My Team tab) with a Japanese team name while using the Japanese locale would display correctly on the My Team list, but selecting the Japanese-named team generated a "not found" error message, and attempting to edit the team information resulted in an error and the data was not saved. This was an issue with the Japanese characters in the data-transform parameter being double-encoded, and has been fixed.
SR-C36705 · Issue 376310
Filter indicator correctly updated for columns following virtual RD
Resolved in Pega Version 8.1
The filter indicator color was not changing for columns after a hidden column in the RD was filtered; the results were displayed correctly, but the small filter icon was not updated with "filtered" styling (red color) but instead remained as "filter" styling (black color). This was due to the wrong column subscript getting generated for the column after a virtual RD, and has been fixed by modifying GenerategridHTML and GenerateCellContent to put the correct subscript in the filter criteria page.
SR-C36835 · Issue 376391
Performance improvement for RetrieveReportData
Resolved in Pega Version 8.1
Unnecessary processing on pyReportParamPageName in the activity pxRetrieveReportData was causing poor performance. This has been improved by adding a check to skip unnecessary operations in cases where the report definition is invoked from a Data page.
SR-C36874 · Issue 382948
Target object handling updated for post-download anchor tags
Resolved in Pega Version 8.1
Once an attachment was downloaded, clicking on anchor tags with href as "#" triggered a browser history popstate event which navigated the page to the Work List. This was due to the code fixing on an incorrect event object, and changes have been made to resolve to the correct target.
SR-C36918 · Issue 382619
PageList properties for List assertion resolve to correct class
Resolved in Pega Version 8.1
Errors indicating "pyStepPage can not be empty for List card" occurred when attempting to save Strategy related Test cases. This was traced to the system not not resolving to the correct class instance type when loading PageList properties for List assertion in strategy related Test cases, and has been corrected.
SR-C36918 · Issue 382615
Truncation added to handle creation of test case label >64 chars
Resolved in Pega Version 8.1
Attempting to create a strategy-related test case failed if the test case label given was more than 64 characters. To better handle this limit, specific code has been added to form a test case label that will truncate it to 64 characters if the label of the test case exceeds that limit.
SR-C37168 · Issue 378659
Check added to ensure autocomplete off is honored
Resolved in Pega Version 8.1
Clicking on the Auto complete control in the Google Chrome browser automatically suggested values stored earlier. To fix this, a check has been added in order to handle browsers that do not honor the standard autocomplete value of "off".
SR-C37273 · Issue 379523
Support added for creation of tags in local alphabets
Resolved in Pega Version 8.1
In order to support the use of other alphabets to create tags in the KM application, validations of regular expressions have been moved from the pxCreateTag to a new activity called pyValidateTagName which can be overridden as needed.
SR-C37311 · Issue 375813
Changed refreshSurvey to use pega.util.event to get the event object
Resolved in Pega Version 8.1
An issue was seen where it was not possible to select an answer on a survey. This was due to Firefox not honoring 'window.event', and has been resolved by modifying refreshSurvey to use pega.util.event to get the event object instead of window.event.
SR-C37339 · Issue 377590
Catch block added for EOF exception in Connect-REST
Resolved in Pega Version 8.1
When running the data page with rest connector as source that invokes a Connect-REST with another service provider, the response was returned as empty. This was traced to an end-of-file (EOF) Exception generated when content encoding is gzip and chunked body is empty. To fix it, a catch block for EOF exception has been added to the copyToBuffer method so that it returns an empty byte array this case.