SR-C79762 · Issue 419158
Decision table decision shape produces correct connector
Resolved in Pega Version 8.1.3
After adding a decision shape and making its type "Decision Table", the connector that was automatically built showed the condition type as "Result", but incorrectly labeled it as a When rule. This was traced to a missed use case in the decision related connectors, and has been corrected.
INC-125972 · Issue 604083
Improved resolved rules cache
Resolved in Pega Version 8.4.4
When Rule resolution iterated over a candidate list to fetch a candidate, performance issues were seen on very large sites. To resolve this, an enhancement has been added that will cache the resolved virtual table entries to optimize performance in high demand use cases like DSM.
INC-137775 · Issue 583783
Improved resolved rules cache
Resolved in Pega Version 8.4.4
When Rule resolution iterated over a candidate list to fetch a candidate, performance issues were seen on very large sites. To resolve this, an enhancement has been added that will cache the resolved virtual table entries to optimize performance in high demand use cases like DSM.
INC-146114 · Issue 604414
Create Survey routes case correctly
Resolved in Pega Version 8.4.4
The Create Survey utility was not routing the case to the user who initiated the case, but instead was routing it to the user who checked-in the case. This was traced to an error related to pxRequestor.pxUserIdentifier in the data transform pzpopulate survey params which is called when the survey utility is used, and has been corrected.
INC-154826 · Issue 614818
Enhanced handling for screen/non-screen/screen flow movement
Resolved in Pega Version 8.4.4
When using a screen flow where the last screen had a link to launch a section, a cancel button in the section that was configured with a data transform and a 'Finish Assignment' intended to move back to the screen flow did not work as expected. If a browser refresh was performed and then the cancel button was clicked, the Finish Assignment / return was triggered as expected. Because this configuration navigated to a non-screen flow, the attachOnLoad function did not load the parameter needed for maintaining error messages. This has been resolved by updating the navigation to handle this use.
INC-144709 · Issue 608797
Removed unnecessary decoding from GetDropdownOptions
Resolved in Pega Version 8.4.4
When using a dropdown sourced by a data page with parameters in the section, passing multiple values as the parameters of the data page resulted in the error "pzGetDropdownOptions:Invalid JSON Stream for data page params" and the parameter values were not resolving at runtime. This was traced to unnecessary decoding in the process, and has been resolved.
INC-208818 · Issue 704708
Corrected intelligent routing in email channel
Resolved in Pega Version 8.8
Intelligent language-based routing in the email bot channel was not working as expected when given a condition to direct messages to a different operator based on language. Messages were placed in the Inbound Correspondence work basket instead. This was traced to the getRoutingActions API using the incorrect property from .pxAnalysis, and has been resolved.
INC-219341 · Issue 715051
Check added to ensure StepPage generation for Top keyword
Resolved in Pega Version 8.8
A ClassCastException was thrown when top page is used, indicating "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl cannot be cast to com.pega.pegarules.pub.clipboard.ClipboardPage". This has been resolved by adding a check which will generate a myStepPage for Keyword "Top" as necessary.
INC-194564 · Issue 700782
Cancel button shown as expected in modal dialog on Mobile
Resolved in Pega Version 8.8
A modal dialog in a mobile app used to show all the phone numbers of a customer did not display a Cancel (close) button after update even though the cancel button was defined on the underlying PhoneNumbers section. This has been resolved by adding a check to assess if the button is visible when calculating modal height.
SR-C77107 · Issue 417089
Added check for sending email attachments with XML data
Resolved in Pega Version 8.1.3
When using SendEmailNotification to send an email with an attachment, the attachment was added but had no content when the email was received. In this case, if the property pyRemoveXML was true and if the email attachment content had XML data and did not contain a <pagedata tag, then the removeXML() method was returning "" as the email attachment content. This has been fixed by adding a check so if the property pyRemoveXML is true and if the email attachment content has XML data and doesn't contain the <pagedata tag, then it will return the original content itself.