SR-D39302 · Issue 507980
Report name in tab uses localization
Resolved in Pega Version 8.3.1
After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.
SR-D39601 · Issue 509517
RRDisplaySection made available to assist Edge compatibility
Resolved in Pega Version 8.3.1
When the Pega Platform was being used with Microsoft Internet Explorer Compatibility Mode ON, it was not possible to use the select filter gadget due to a browser compatibility issue: enabling the filter condition for the report definition caused the SelectValues button to stick in loading mode when clicked. Changing the Microsoft Internet Explorer Document Mode for Harness pzRRDisplaySection to Microsoft Internet Explorer =Edge corrected the issue, but the rule was final. To resolve this, the pzRRDisplaySection has been made available to allow override for customers still using Microsoft Internet Explorer .
SR-D40599 · Issue 508279
Handlign added for Japanese half-space character during DB query
Resolved in Pega Version 8.3.1
After creating a Report Definition based on the Unicode/Japanese text property with summary list, the list was visible from Report viewer but any full size space used by the summary filter was unintentionally trimmed to half size space. As a result, the database query could not find the item. This has been resolved by modifying the setGroupByInputs API in the pega_report_summary js file to use the unicode space char(\u0020) instead of \s in regex. The Japanese space character will be replaced in the pzDrillDownReport activity step 2 for the query use, and will be set back to the Japanese space character in pyFilterValue.
SR-D42138 · Issue 509288
Fixed white space issues with Previous and Next buttons in multi-page Audit Reports
Resolved in Pega Version 8.3.1
After upgrade, multiple-page Audit Reports in GOC had too much white space between the end of the numbers and the Next Button, and the Previous Button had too much white space between 'Previous' and the start of the numbers. This was traced to a coding error in the pzbase-browser CSS generation that resulted in a space between "div" and "[node_name="pyGridPaginator"]". This has been fixed. Unused webkit selectors have also been removed.
SR-D17306 · Issue 490918
RD pagination expanded to 1500 rows
Resolved in Pega Version 8.3.1
The default pagination enabled on the Report Definition was limiting the results to 50. This has been enhanced to a row limit of 1500 in report definitions pzGetAllPropertiesOfGivenClass.
INC-
218457 · Issue 713986
Updated debug logging
Resolved in Pega Version 8.7.2
Debug logging within IndexReferenceSynchronizer and FastLoader has been updated. With this update, IndexReferenceSynchronizer debug logging will indicate what the action is for each instance, FastLoader will include information about the keys being loaded and statements being executed, and duplicate logging has been removed from BatchSQLExecutors.
INC-202004 · Issue 705170
Hotfix documentation updated to point to Hotfix Manager page
Resolved in Pega Version 8.7.2
The readme file attached to hotfix downloads contained an outdated reference to use "PRPC Hotfix Installer on the Update Manager landing page." This has been updated to point to the Hotfix Manager landing page.
INC-205181 · Issue 697801
Warnings pull from report definition page
Resolved in Pega Version 8.7.2
When a report definition filter was used in the "Class instances to include" section of the Product rule, severe warnings appeared noting "Report definition filter performance issues for LookupDataMigration : Using a custom HTML control to format a column may result in poor performance displaying query results. Consider using auto-generated HTML controls". However, the report definition used, LookupDataMigration, has no Custom HTML control in the latest version of the rule, and the "CheckForWarnings" rule for the product was running a report definition in the "Index-Warning" class which has the warnings for all the versions of the rule. This was due to warnings being displayed in the product for the report definition filter without applying rule resolution for report definition, resulting in warnings from all report definition version rules from a ruleset given a report definition name. This has been resolved by adding an update which will use Obj-Open to read the warnings from report definition page instead of looking up for warnings from Index-Warnings table.
INC-205453 · Issue 706570
Pega Keystore supported for hotfix signature verification
Resolved in Pega Version 8.7.2
In order to support custom trust managers which require an alternate method for supplying the root certificate via a platform trust store, an enhancement has been added to allow Pega Keystore to be used as a hotfix verification source. Detailed information on this can be found in https://docs.pega.com/keeping-current-pega/87/verifying-hotfix-authenticity-using-pega-keystore
INC-208516 · Issue 705099
Patchdate values made unique
Resolved in Pega Version 8.7.2
The hotfix manager was incorrectly indicating that a previous hotfix was not installed or was partially installed and should be reinstated. This scenario was created during security updates where the missing/incomplete hotfix had been deliberately deleted from the database, and has been resolved by adding an update which will force patchdate to be unique when adding duplicate code resources during tests.