INC-157974 · Issue 621966
Summary Report collapsible sections made accessible
Resolved in Pega Version 8.6
In order to improve accessibility, the rules 'RRDataSummaryGeneration' and 'pzDisplayGroupNodeVertical' have been updated so the clickable expand icons in summary reports will append the value of the current group when setting the text "Click to expand or collapse". This will allow JAWS to uniquely identify exactly what will be expanded or collapsed.
INC-158473 · Issue 626277
BLOB decryption API updated for greater flexibility
Resolved in Pega Version 8.6
A BIX extraction issue occurred after the class had enabled BLOB Encryption. The errors indicated the BLOB had been persisted in an incorrect stage, causing the extraction of the single item to never complete even though some CSV file was created. This was traced to the API used to read the encrypted BLOB, DatabaseUtilsCommonImpl.getStreamBytes, which had the limitation of decrypting only when a Site-specific cipher existed. To resolve this, the system has been modified to use a different API which works for all encryption modes, PageDatabaseMapperImpl.getStreamBytes().
INC-158874 · Issue 625384
Zero value parameter handling added to Trend Reporting
Resolved in Pega Version 8.6
After converting the Summary Views to a Report Definition, the Chart reporting functionality was not working in the Report Definition drill-down reports; whole records present were being fetched instead of only the graph chart count. Investigation showed that one of the parameters in the FilterBy was missing, and that pxSLAAgeTimeliness used 0 instead of null, causing the system to consider all records. This has been resolved by modifying the pega_report_Summary.js file and the pxSLAAgeTimeliness FunctionAlias to handle the 0 value and ensure all parameters are present.
INC-159399 · Issue 626767
Report styles color contrast enhanced for accessibility
Resolved in Pega Version 8.6
In order to improve accessibility, pzReportBrowserStyles has been updated to change the report creation info color to #00000 to enhance the contrast.
INC-159759 · Issue 629624
Report title displayed for empty widget charts
Resolved in Pega Version 8.6
Per design if there is no data to be rendered in the chart from a report added in a Widget in any portal, a static image is displayed saying "No Data to Display". However, if there were multiple reports in the Widget it caused confusion on which report was not being displayed because the image did not show the title of the report. To resolve this, an enhancement has been added to modify pzRRChartDiv to display the report Title even when there is no data in it.
INC-160178 · Issue 632897
Local time used for report filters
Resolved in Pega Version 8.6
The date format in the filter condition of the report was being displayed in GMT format rather than the Local time Format. This has been corrected.
INC-160825 · Issue 629369
Search landing page performance improved
Resolved in Pega Version 8.6
Performance improvements have been made for the Pega Platform search landing page by implementing timeouts for all requests to ElasticSearch when executing PegaIndexAdminImpl.getIndicesInfo() and changing all requests for single index to requests for all indexes. In addition, SearchUtils.areDummyDocumentsPresent() has been modified to get all 'dummy documents' in case there are duplicate dummy documents in the ElasticSearch indexes.
INC-SR-D91660 · Issue 555725
Updated document ID handling for deleting indexes
Resolved in Pega Version 8.6
When trying to delete a document for index name "work*", intermittent errors were seen indicating an invalid index name or index does not exist value. This has been resolved by updating the handling for delete by ID.
SR-D27161 · Issue 503154
Step staus fail logic updated to handle agent activity exception
Resolved in Pega Version 8.2.4
Attempting to execute an advanced agent containing logic that set a step status to fail resulted in the error "Agent activity disabled due to execution errors; ErrorMsg: unable to execute agent: Cannot obtain a lock on instance as Requestor already has the lock ". This was traced to a backwards compatibility issue with previous work done to handle cases where agent activity requires authentication and agent has "bypass auth" flag set to false. Agent activity is not allowed to execute by the engine, and to show this scenario as exception case instead of showing it as running in admin studio, changes were made to rely on step status as the engine internally sets step status to false in this case. However, this inadvertently affected use cases where agent activity sets the status as fail in its logic. To resolve this, the system has been updated to handle the exception case and not consider StepStatus.
SR-D38492 · Issue 505489
Batching now enabled when using IH Summary shape in substrategies
Resolved in Pega Version 8.2.4
Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected.