SR-C32155 · Issue 374359
Null check added for empty clipboard page in GetPopOverData
Resolved in Pega Version 8.1
When first launching a screen which contains a repeat grid, the table definition contains a prim_page value like "TempSelectedCustomer". Clicking the filter icon on any column of the repeat grid then caused the pzGetPopOverData activity to be fired from the UI with the parameter preActivityPage and value "TempSelectedCustomer", but there was no such page in the Clipboard and an exception was generated. If the browser was refreshed and the same scenario run again, pzGetPopOverData activity was fired from the UI without the parameter preActivityPage and no issue was seen. To resolve the error on the first pass, a null check has been added to the pzGetPopOverData activity first step.
SR-C32269 · Issue 377440
Section rendering error after tab switching fixed in Microsoft Internet Explorer
Resolved in Pega Version 8.1
When using Microsoft Internet Explorer , clicking on a tab after expanding some collapsible layouts on a previous tab resulted in a 'cannot render section' error. This was traced to the handling for the event target in Microsoft Internet Explorer not resetting the thread back to the base-thread when the third tab was clicked, and has been fixed by modifying the resetExecutionThread method to take the activeElement into account when dealing with focusout in Microsoft Internet Explorer .
SR-C32295 · Issue 372890
Emails sent from Service Request template created correctly
Resolved in Pega Version 8.1
When an application was created from the 'Service Request' template via Pega Express, emails sent had a blank body. This did not happen with applications built from the Custom template. This was traced to the Send Email smart shape internally calling pzSendEmail which then calls SendSimpleEmail activity. This activity was available both in Work- and PegaSample, and as this case type class was inherited from PegaSample, it picked SendSimpleEmail from the PegaSample class and resulted in a dummy implementation. To fix this, SendSimpleEmail has been withdrawn from the PegaSample class so that same rule from Work- will be picked.
SR-C32412 · Issue 376002
Jackson and ElasticSearch upgraded
Resolved in Pega Version 8.1
ElasticSearch (in embedded mode) has been upgraded to ES 5.6.7 so that nested structures can be accommodated in ElasticSearch when using dynamic templates. In addition, the Jackson JARs have been upgraded to version 2.9.5 for improved security.
SR-C32546 · Issue 372538
Decision Table evaluation logic repaired
Resolved in Pega Version 8.1
A logic flaw was found when doing the division of nCondRowLimit with 1000. If nCondRowLimit was 30, i.e. 1000%30=10, 10 rows were missing when evaluating the decision table. The logic has now been modified to correctly evaluate the right row from the decision table.
SR-C3261 · Issue 348618
Performance improvement for Stream API
Resolved in Pega Version 8.1
Some of the APIs from stream processing were creating unnecessary objects and causing higher memory consumption. The behavior has now been changed to optimize frequently used APIs to improve performance.
SR-C32714 · Issue 372496
Customizable pyHistoryMemo value added to pzCreateCaseFromInteractionCase
Resolved in Pega Version 8.1
While performing triage when using an Email interaction case, the attachments are copied into the newly selected change stage and the audit shows an entry for each attachment, i.e. they have multiple entries for multiple attachments. In order to make the audit more informative, the field value "pyHistoryMemo" has been created and added to the pzCreateCaseFromInteractionCase activity to allow customized configuration for AuditNote.
SR-C32739 · Issue 372485
Credentials sanitized when logging exception for invalid primary page name
Resolved in Pega Version 8.1
Whenever an invalid primary page name was passed along with credentials in queryString, the credentials were logged without sanitizing or masking. Current standard behavior is that flows are run in an authenticated session that would not be passing this information, but this scenario was traced to legacy code for a very corner case that was not transitioned to the more secure method. The error information will now be properly sanitized on logging an exception.
SR-C32911 · Issue 373513
Submit button no longer shows <u> tag when accessibility enabled
Resolved in Pega Version 8.1
When a user was accessibility enabled and there was a custom filter section for a report, the Submit button in the pzRRDisplayCustomFilterSection section incorrectly showed "<u>S</u>ubmit" as its label. To correct this, the button has been updated to a new Auto-Generated button and script on click has been added.
SR-C32943 · Issue 372905
Values correctly generated for elements with attributes in ParseXML134
Resolved in Pega Version 8.1
The new SOAP integration wizard was not creating "Value" properties in WSDL with several ComplexType elements using SimpleContent definition, though it did create properties for all the attributes. This resulted in data mapping anomalies. This was traced to a missed use case in rule generation, and the rule generation implementation has been updated to generate the "Value" property for ComplexType element with SimpleContent and configure it in the mapping rules.