INC-172521 · Issue 651551
Email template content visible in user application
Resolved in Pega Version 8.5.4
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-174699 · Issue 652070
Work objects can open in multiple tabs with Layout group
Resolved in Pega Version 8.5.4
After implementing the Worker portal with Layout Group(Tab) to open work objects and other options (Pulse, Spaces, My Cases etc.) in multiple tabs, the tabs opened as expected the first time but after all of the tabs were closed any newly opened cases appeared in popup windows instead of tabs. Investigation showed that when the last tab was closed, the display was set to the main div container of the ajaxcontainer so opening the work object again used a new window. Tab Group has been deprecated in the current Pega version, but the site has a requirement to open the cases in same way as they appeared with Tab Group; to resolve this, support has been added by making the width 0 for the active header highlighter instead of using display none for the main container for this configuration.
INC-174921 · Issue 652320
Client Side required validation applied to dropdown Date field
Resolved in Pega Version 8.5.4
The mandatory validation on submit of the screenflow screen was not being triggered even though 'Required' was configured on the Date field.This was traced to the validation being applied to a hidden field when the date time control is configured in dropdown mode, and has been resolved by adding a condition for validating this configuration.
INC-155878 · Issue 645364
Class list updated when using ActivateDocument in portal navigation
Resolved in Pega Version 8.5.4
Global search worked the first time it was used, but failed after another case was opened from the dashboard or there was a click on any landing page home, dashboard, or space. Investigation showed this was caused by the pySearchText being blank in the clipboard, which was traced to a harness context issue related to pega.desktop.activateDocument being used in pzPortalNavigation on DynamicLayout with Application Logo and Application label. To resolve this, an update has been made that will update the class list with the proper one when the data-harness-id is set.
SR-C40145 · Issue 402928
Restarting the SVM training analysis checks for existing model request to continue
Resolved in Pega Version 8.1.1
When creating a predictive model there was an issue with completing the SVM training analysis either due to error or browser crash. In previous versions of Designer Studio the session would stay alive and continue to execute, however more recent versions of the decision analysis's portal expected the user to keep the session active in order for the model to complete even though for long-running model training it is not viable to keep a session open for many hours. This was caused by the model generation process being kicked off again when the wizard was relaunched, and has been resolved by adding a check to the relaunch that will look for an existing model generation request and continue with the same request if one is found.
SR-C42849 · Issue 402885
Validation corrected to honor Read-Only designations
Resolved in Pega Version 8.1.1
Validation was happening on Read-Only fields due to pyReadonlyValidation not being honored in all editable cases. This has been corrected.
SR-C46537 · Issue 402866
Code added to format location header for redirect response in IE
Resolved in Pega Version 8.1.1
When using Internet Explorer, authentication was working but the portal did not load. This was traced to IE mandating the presence of a location header in the response: an HTTP 303 "See Other Response" was being returned along with the initial portal HTML payload, but recent modifications to SAML 2.0 to use the PRAuth Servlet were missing this specific redirect case. To resolve this, generic code has been inserted that adds the location header in all redirect cases.
SR-C46793 · Issue 402870
Fixed single logout for Mashup applications and updated logging for pzAuthServiceSelector
Resolved in Pega Version 8.1.1
When the GOC (Global Operations Console) application was added as a mashup application to MSP (My Support Portal), logging off from MSP showed the GOC session in a disconnected state despite them using the same SSO application service. The issue was traced to homeurl not being stored properly in mashup use cases, and has been resolved by getting the property homeurl from pxRequestor page instead of pxThread page. In addition, the pzAuthServiceSelector activity was including an 'infoForced' log message. Although the redirect URI does not contain any confidential information, the 'state' parameter should not be visible in logs. This has been handled by changing oLog.infoForced to oLog.debug().
SR-C48056 · Issue 402881
RRChartDiv tries resize three times before exiting to prevent high CPU usage
Resolved in Pega Version 8.1.1
Very high CPU usage was reported when two or more tabs were open, even when there was not actual work being performed in the app. This was traced to a chart in Team Dashboard that was displayed with "No data to display"; because the toolbar height was always 0, the resize callback was going into an infinite loop. This has been fixed by modifying the logic in pzRRChartDiv to only try the resize three times to get the height of toolbar or slider before exiting.
SR-C49844 · Issue 402924
Added check for external Cassandra cluster to avoid unnecessary DDS pulse error logging
Resolved in Pega Version 8.1.1
After upgrade, DDS pulse errors were filling up the jvm.out logs. This was caused by a check in system_auth keyspace that was redundant for sites running their own Cassandra cluster (external). To fix this, DDS pulse operation will check If the Cassandra cluster is external; if it is, it will not check system_auth keyspace and will Omit DDS pulse operation actions except update logging.