INC-220837 · Issue 729122
Number formatting a separator corrected for Greece
Resolved in Pega Version 8.8
When the locale was set to el_GR, number formats for currencies in monetary digit grouping was using 3;2 formatting instead of 3, causing errors such as 10,00,000.00 being displayed instead of 1.000.000,00. This has been corrected.
INC-209071 · Issue 706038
Other Currency resolves value in Pega DX
Resolved in Pega Version 8.8
When using Pega DX with the pxDisplayText currency set to "Other currency", only the property name was sent as part of the metadata and not the actual value. This has been resolved by updating "Other currency" to resolve the property reference and get the value.
INC-232010 · Issue 740693
Report filter error message persists on the screen
Resolved in Pega Version 8.8
When attempting to use an invalid report filter such as "past 14 days" when that timeframe was not available, the error message appeared briefly and then disappeared. Investigation showed the runReport activity pzResolveCopyFilters activity was called and caught the “Invalid value” exception, however the system continued to proceed so the error message did not persist in the screen. This has been resolved by adding a jump condition to step 2 of pzResolveCopyFilters on StepStatusFail to preserve the error message.
INC-215877 · Issue 715234
Handling added for Oracle "NUMERIC" type
Resolved in Pega Version 8.8
When a product rule was created in an environment using Oracle, importing the product into the cloud environment with database table schema changes resulted in errors. This was traced to a change in Oracle's JDBC driver which was reporting Number as a JDBC "NUMERIC" type instead of the previous "DECIMAL". Pega uses the NUMBER data type and expected a type=DECIMAL for an Oracle number, causing the errors. This has been resolved by adding a check for flex numbers if column is NUMERIC.
INC-200030 · Issue 698955
Handling added for external Kafka authorization exception
Resolved in Pega Version 8.8
When using external Kafka for stream service, the dataflow was failing with the error 'QueueProcessorDataSubscriberException' when topic create permission was missing. As a workaround, the topics could be pre-created, though a "Topic already exists" warning was generated. To resolve this, the cluster-wide right that a producer needs, IdempotentWrite, has been added. For more information please refer to the link https://docs.confluent.io/platform/current/kafka/authorization.html
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-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.