Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-185847 · Issue 668984

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.5.5

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

INC-187057 · Issue 661617

Pega reference tags persist

Resolved in Pega Version 8.5.5

Cross-site scripting protections have been updated to allow Pega reference tags.

INC-167606 · Issue 657153

Optimization prconfig check added for TableInformationMap

Resolved in Pega Version 8.5.5

A prconfig setting check has been added to the TableInformationMap use of OPTIMIZE_SMA_QUERY during its foreign key lookup.

INC-168368 · Issue 657028

DateTime validation works correctly after importing invalid data

Resolved in Pega Version 8.5.5

After creating DecisionData (Dev studio) and adding a DateTime property to the form, importing records with invalid DateTime values failed with a validation error on the screen and the message "Error while converting format for data type DateTime property name Test_date_format with value scvf" was logged. Attempting to proceed by correcting the DateTime property and uploading worked, but any subsequent imports in the same session silently allowed invalid inputs to be passed without any validation errors and then showed blank date fields. This has been corrected.

INC-169636 · Issue 659533

Navigation icons added for use in offline mobile

Resolved in Pega Version 8.5.5

When using an offline mobile app, clicking on an image / link on the home page for navigation resulted in the error “Resource missing. See client logs.” This was traced to a missed use case that resulted in some icons not being available in the package, and has been corrected by including the following:webwb/py-menu-toggle.png webwb/pzgrid_downarrow.png webwb/pymenuleftarrow.png webwb/pymenurightarrow.png webwb/pymodal_mask_img.png webwb/py-grid-sort-down.svg

INC-170514 · Issue 651709

Filtering updated for UI markup

Resolved in Pega Version 8.5.5

Filtering has been added to the UI code to preserve the browser display appearance but remove inappropriate or potentially insecure markup.

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().

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us