SR-C23134 · Issue 362897
Tab delimiter write-out corrected for File Dataset
Resolved in Pega Version 8.1
The File Dataset was writing out "\t" as the delimiter for tab delimited files. This was due to the tab character being escaped and then treated improperly in the parser/serializer, and has been fixed.
SR-C23134 · Issue 362970
Tab delimiter write-out corrected for File Dataset
Resolved in Pega Version 8.1
The File Dataset was writing out "\t" as the delimiter for tab delimited files. This was due to the tab character being escaped and then treated improperly in the parser/serializer, and has been fixed.
SR-C23138 · Issue 367878
PRPushServlet response corrected to 400 when disabled
Resolved in Pega Version 8.1
PRPushServlet is used to establish a WebSocket connection with the Pega server. When server-push is disabled, the Push engine won't get initialized and will return an empty response by logging a warning message ("Request arrived for requestor:[%s]. But PushEngine has not started." ). Unexpectedly, this process was returning HTTP status 200 instead of 400. This has been corrected.
SR-C23153 · Issue 370814
Corrected handling for birthdate of 1970-01-01
Resolved in Pega Version 8.1
Issues were seen when the input date of birth was “1970-01-01” (matching the "epoch date" when time started for Unix computers) in the request of a webservice. When the DSS "disableEpochDate" on "Pega-IntegrationEngine" was set to "true", the date of birth was deleted from the request if it was 1970-01-01. If it was set to "false", other empty Date properties were valued as 1970-01-01 in Stream XML data mapping. To resolve this, the DSS setting will only be considered when the Date/DateTime property value is not empty.
SR-C23157 · Issue 364333
JMSListener modified to support custom connection client ID
Resolved in Pega Version 8.1
If JMSListener was configured for PubSub messaging model with durable subscription, restarting the JMSListener generated a new ClientID that was used to retrieve messages from Topic. This resulted in either some messages being missed or some being processed multiple times. To resolve this, a new configuration/field has been introduced on the JMSListener ruleform that accepts a client ID that can be specified statically/dynamically per listener.
SR-C23250 · Issue 365591
Corrected column count calculation for DT with property set
Resolved in Pega Version 8.1
If a decision table was configured with property set in output instead of any return column,after exporting the content of the decision table into Excel a Return column appeared in the Excel file. If the same Excel data was imported after modifying it, a spurious column was added on the right side of the Decision Table. This was caused by the property-set calculation of the column count not being considered properly, and has been corrected.
SR-C23410 · Issue 363298
Customization added to Report Browser
Resolved in Pega Version 8.1
In order to support customization of the Report Browser, the below rules are now marked as available:PZRBSHORTCUTSGRID7 PZRBREPORTACTIONS RULE-HTML-HARNESS CODE-PEGA-LIST DISPLAYREPORT #20151123T213308.460 GMT RULE-HTML-HARNESS CODE-PEGA-LIST PZRRDISPLAYCUSTOMFILTERSECTION #20160512T224721.208 GMT Schedule options and Shortcut/Category options can be hidden via 'when' rules: pyReportBrowser_ShowActions should be set to False to hide the shortcut/category actions, and pyReportBrowser_ShowSubscriptionActionsAndInfo should be set to false to hide the report subscription information. When both rules are set to false, the gear icon on the shortcuts grid and list of Public categories will not be displayed. In addition, the DisplayReport and pzRRDisplayCustomFilterSection harnesses have been made available to allow changing the Microsoft Internet Explorer Document mode.
SR-C23461 · Issue 365026
Exported Excel now displays text between angle brackets
Resolved in Pega Version 8.1
Using the Export to Excel feature on a Report Definition was stripping XML and HTML-like values from the data such as text between matching angle brackets. This was traced to recently modifications in Export to Excel: because the export generates an XLSX document and not an HTML document, HTML-like code is stripped from formatted values. However, that was being performed after unescaping special HTML characters and codes in the raw or localized value, and this caused HTML-like code in the data to be removed as well. To correct this, the system will strip HTML prior to unescaping special characters. In addition, columns which did not have valid controls assigned to them or their associated properties were borrowing logic from columns formatted by non-auto controls. This has been addressed by refactoring ReportUIFieldFactory to generate basic ReportUIField instances for unformatted columns, excluding numeric and date columns.
SR-C23556 · Issue 364797
JAWS reads table sort order
Resolved in Pega Version 8.1
To improve accessibility, the sort order of a table will be read by JAWS.
SR-C23560 · Issue 378135
Accessible 'select' button added to date/dropdown with post value
Resolved in Pega Version 8.1
An enhancement has been added to the pzpega_ui_template_dropdown.js file in the PegaWAI ruleset to allow any date / dropdown with a post value to be provided with a "Select" button when accessibility is enabled.