INC-170918 · Issue 653216
DateTime property handling revised for future date with daylight savings time
Resolved in Pega Version 8.7
A DateTime property was changing each time the local action refreshed. Investigation showed this was a missed use case related to recent work to correct an issue with a 1 day discrepancy for non-template DateTime. The previous update to use the default time zone when generating markup in non-template for the date property while the datetime property uses the server time zone has been further refined to handle formatting the date time when the year is greater than 2037 and combined with daylight savings time. This will be resolved by setting the correct date before returning the moment object if the year is greater than 2037 for the date time control using display mode as date.
INC-175994 · Issue 667482
Removed redundant Microsoft Outlook email interaction chain
Resolved in Pega Version 8.7
When opening an email interaction case, the email editor user interface area showed the complete email chain of the email for every new message that came in related to the case. This was traced to the difference in the selectors that various email clients use to construct a response to an email with email history in it, and has been resolved by updating the selectors for Microsoft Outlook in pyRichTextEmailHistorySelector so no conversation is repeated when using that client.
INC-183822 · Issue 667502
Filename with non-ASCII characters normalized for Apple Safari upload
Resolved in Pega Version 8.7
When using the Apple Safari browser, attaching a file name that contained Japanese characters resulted in an "attachment doesn't exist" error message when trying to open it again. This was caused by the special characters in the FileName for the Data/Query string not being encoded during the file upload, and has been resolved by updating the UploadFileToADocument activity to normalize the FileName if the Safari Browser is being used.
INC-191356 · Issue 679163
External Input setting available on Strategy Batch Performance Test
Resolved in Pega Version 8.7
It was not possible to specify the External Input as part of a strategy when using a Batch Performance test. This has been resolved by updating the pzDisplayTestStrategyContext When condition to "true" the so external input selector is properly displayed.
INC-191902 · Issue 677412
Updated security for importing Excel to a decision table via a delegated rule
Resolved in Pega Version 8.7
An error was seen when attempting to import an Excel file into a delegated decision table when using the case manager portal. This has been resolved by correcting a BAC issue for decision table import in the pzRuleDeclareDecisionTableStandard.js file.
INC-191356 · Issue 679164
External Input setting available on Strategy Batch Performance Test
Resolved in Pega Version 8.6.3
It was not possible to specify the External Input as part of a strategy when using a Batch Performance test. This has been resolved by updating the pzDisplayTestStrategyContext When condition to "true" the so external input selector is properly displayed.
INC-191902 · Issue 677413
Updated security for importing Excel to a decision table via a delegated rule
Resolved in Pega Version 8.6.3
An error was seen when attempting to import an Excel file into a delegated decision table when using the case manager portal. This has been resolved by correcting a BAC issue for decision table import in the pzRuleDeclareDecisionTableStandard.js file.
INC-172521 · Issue 651553
Email template content visible in user application
Resolved in Pega Version 8.7
An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.
INC-125136 · Issue 575998
Topic name prefix support added for Kafka
Resolved in Pega Version 8.5
An enhancement has been added to support the use of site-specific standards for the naming of queues. This can be used to add clarification between Kafka Topics created by Pega and those created for internal topics when using a shared Kafka Cluster. This is done using the new setting: <env name=”services/stream/name/pattern” value=”prefix{stream.name}postfix”/> . As an example, if tenant.name is resolved into "myco" and the environment into "prod1", value="{tenant.name}-{environment}-{stream.name}" will result in stream myco-prod1-{stream.name} By default, when stream.provider = EXTERNAL, the default will be “pega-{stream.name}” .
INC-178116 · Issue 660565
Article on configuring display options for a harness updated
Resolved in Pega Version 8.7
The documentation around the load behavior of a harness has been updated to reflect that the initialization settings only apply when using the harness as a landing page from the channel config. Applications that use Cosmos React do not use harnesses for landing pages. You can modify Cosmos React landing pages only in App Studio.