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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-188127 · Issue 678350

Updated cache key generation for ROPC

Resolved in Pega Version 8.8

After configuring outbound email functionality using MSGraph with OAuth 2.0, sending the emails failed consistently following passivation. Running "Test connectivity" in the Email Account data instance then seemed to restart the functionality and the automation "Create And Send Email" subsequently worked. This was traced to a missing username in the cache key generation for the Resource Owner Password Credentials (ROPC), which caused the same token to be fetched when attempting to dynamically generate different usernames, and has been resolved.

INC-225257 · Issue 730293

Pega DateTime supports pre-1970 timestamps

Resolved in Pega Version 8.8

The function getTimeStampAsDateStamp from Pega DateTime class was not working correctly for dates before Jan 1st, 1970. Support has now been added for this use.

INC-148272 · Issue 608999

Increased specificity for collapsed DL

Resolved in Pega Version 8.6

When using the collapsible header functionality of a container skin format, the styling was not being applied correctly to the header. This has been resolved by increasing the specificity for a collapsed dynamic layer.

INC-149953 · Issue 613728

Increased specificity for collapsed DL

Resolved in Pega Version 8.6

When using the collapsible header functionality of a container skin format, the styling was not being applied correctly to the header. This has been resolved by increasing the specificity for a collapsed dynamic layer.

INC-216162 · Issue 718923

GetNextWork uses correct tabname

Resolved in Pega Version 8.8

Clicking on Get Next was showing the tabname as "Next" instead of the caseid when using the handleMdcTabs function. This has been resolved by setting the correct tabName in case of getNextwork.

INC-232204 · Issue 738834

List Report opens in new tab

Resolved in Pega Version 8.8

Every time the results of the List report was clicked, the UI was refreshed and the case opened in the same screen with filter criteria removed. This was traced to "pega.desktop.infinity.openHandleInNewTab" being added in the "pzRDWinTitle" control, which is referred in the "pzReportDisplay" section. As the "Apply filter" button action set is not refreshing the "pzReportDisplay" section, the original function "pega.desktop.infinity.openHandleInNewTab" was getting replaced with "openWorkByHandle". This has been resolved by adding the conversion of the openworkbyhandle function in the header of the table.

INC-164944 · Issue 636291

Logic updated to handle decision trees over 64k

Resolved in Pega Version 8.6

An exception was thrown when decision trees reached the 64K size limit. This has been resolved by modifying the logic in the DecisiontableMethodBody Rule-Utility-Function where the split size nPropRowLimit is based on the number of columns.

INC-137100 · Issue 604059

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.2.8

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

INC-137100 · Issue 604058

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.6

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

INC-131151 · Issue 572831

Resolved empty body for Reject email

Resolved in Pega Version 8.2.8

When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.

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