SR-B39878 · Issue 299678
Fixed encoding of colon for exported report title
Resolved in Pega Version 7.3
A file exported using Chrome or Mozilla displayed %3A instead of Underscore (_) when replacing a colon in the title. This was an error in the encoding, and has been fixed.
INC-192769 · Issue 683001
Removed incorrect role from accessible filter logic
Resolved in Pega Version 8.7
When using JAWS, tabbing out from Close(X) and setting focus on the "filter by" section resulted in JAWS reading out "use arrows to move". This was not an available action, and has been resolved by removing role="listitem" from the RRFilters_logic.
SR-B39673 · Issue 297670
Fixed grid row editing for Remote List
Resolved in Pega Version 7.3
When trying to create a property with table type as Remote List, it was not possible to edit or add the rows. This was due to the grid using the row editing option 'None' when the grid row-editing property has been changed to 'inline', and the table editing has been changed to inline.
INC-147873 · Issue 610864
Custom header character encoding for Subject added
Resolved in Pega Version 8.4.4
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
SR-C71043 · Issue 416762
pzSendEmail returned to revious behavior of sending separate emails to work parties
Resolved in Pega Version 8.1.3
After upgrade, a change in behavior was seen when using the pzSendEmail activity. When pzSendEmail was called to send emails to work parties, a single email is sent to all recipients instead of separate emails to each recipient as it did in earlier versions. The SendSimpleEmail activity accepts a SendDiscreteMails parameter, the pzSendEmail activity has 'Pass current parameter page' checked so the default value for the SendDiscreteMails parameter was not used. This was a backwards compatibility error, and has been corrected by setting the SendDiscreteMails parameter to true by default in the pzSendEmail activity.
INC-159244 · Issue 627863
Bulk actions check in preserves declare expression legacy setting
Resolved in Pega Version 8.7
When a declare expression was saved in legacy mode with "Whenever used" selected in change tracking, performing a bulk check-in of the rule caused the expression to default to the new forward chaining method. This did not occur when using a direct check-in. Investigation showed this was caused by the check-in page holding a legacy value before the step execution, and has been resolved by adding a pre-save activity before the validation activity that will restore the .pyIsLegacy value from .pyExpressionTypeSelector, if set.
INC-208424 · Issue 707613
Custom header character encoding for Subject added
Resolved in Pega Version 8.8
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
SR-B43160 · Issue 299701
Fixed up/down arrows for Firefox modal dialogs
Resolved in Pega Version 7.3
Up and Down arrows actions were not working in modal dialog text boxes when using Firefox. This was a defect in the framework, and has been addressed in modaldialog js.
INC-174020 · Issue 650891
Performance improved for Directed Web Access (DWA)
Resolved in Pega Version 8.7
Slowness when using a Directed Web Access (DWA) link has been resolved by refining the code of the PZPEGA_UI_DOC_EVENTSCONDITIONSCHAINING script to improve performance.
INC-199469 · Issue 707514
PDF margins made available as parameters
Resolved in Pega Version 8.8
After update, margins were different in exported PDFs. This was due to upgraded jar files: PD4ML v3 used setPageInsets(new Insets(top, left, bottom, right)) , but the v4 jar uses setPageMargins(new PageMargins(left, top, right, bottom)) . Because the order of values (20, 10, 10, 10) were not changed this produced a different result. To resolve this, PD4ML margins are now available to be set as parameters: Param.pyMarginLeft, default value 20 Param.pyMarginTop, default value 10 Param.pyMarginRight, default value 10 Param.pyMarginBottom, default value 10 When standard activities like HTMLToPDF / pyViewAsPDF / pyAttachAsPDF are used, add a Property-Set step before calling the activity to add the necessary margin parameters. When CreatePDF smart shape is used, set the parameters via the connector of the CreatePDF.