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.

SR-B71423 · Issue 319981

Localization added to pyAccountSettings field labels

Resolved in Pega Version 7.4

Field label localization for the pyAccountSettings section rule has been added to the Pega-IntegrationArchitect ruleset.

SR-B73542 · Issue 327654

JNDI Server field in Connect-JMS supports GRS

Resolved in Pega Version 7.4

Setting the value of the JNDI Server field in the Connect_JMS rule form using Global Resource Setting was only working when the JNDI Server rule instance was specified directly. In addition, attempting to use a GRS to set the value in the JNDI Server field itself resulted in the error "Could not find JNDI Server instance: =D_PegJMS.PegJNDIProp". This was due to the JNDIServerPage receiving the value of JNDIServerName but not being able to use it. To correct this, a local variable actualJNDIServerName has been added to carry the information and make it available to the API.

SR-B74017 · Issue 329731

MimeType set on attachments

Resolved in Pega Version 7.4

In order to correct a problem for mobile users attaching files, pyAttachMimeType will now be set on the pyNewFileAttachment page for both online cases and offline cases.

SR-B76463 · Issue 340030

Refresh from ruleform correctly passes mandatory parameter

Resolved in Pega Version 7.4

The below error message appeared on the clipboard when going to Action tab and clicking on Refresh button: "Unable to load data page D_ServiceMethods. Required parameters : ServiceType. cannot be blank". This warning message was also visible in the logs whenever the service was called from any SOAP client. In this case, triggering a refresh from Ruleform action was not passing a mandatory parameter to the D_ServiceMethods data page. To fix this, the section Grid has been modified to verify the parameter (i.e. pyServiceType) and then display it.

SR-B78159 · Issue 338941

Mobile dashboard widget name value displays correctly

Resolved in Pega Version 7.4

A problem was seen where the dashboard widget name tag was not resolved on the first visit to the dashboard, but after navigating to the second screen on a mobile device and then returning to the dashboard, the correct value appeared. This was traced to a missing use case for a header using JSP format, and has been corrected.

SR-B78159 · Issue 338952

Mobile dashboard widget name value displays correctly

Resolved in Pega Version 7.4

A problem was seen where the dashboard widget name tag was not resolved on the first visit to the dashboard, but after navigating to the second screen on a mobile device and then returning to the dashboard, the correct value appeared. This was traced to a missing use case for a header using JSP format, and has been corrected.

SR-B78996 · Issue 330406

Proxy Support added for "Mobile App Build" Mechanism

Resolved in Pega Version 7.4

The Mobile Application 'Build' mechanism was not picking up on the JVM Proxy Settings (-Dhttps.proxyHost, -Dhtps.proxyPort, -Dhttps.proxySet). This has been added.

SR-B82481 · Issue 333250

added safecheck to sectionRefreshCallback

Resolved in Pega Version 7.4

When doing a refresh of a section in the PSI app, the Hybrid client in function sectionRefreshCallback in pzpega_ui_ajaxengine.js was causing a crash. This was due to a missing safe check which has now been added.

SR-B82678 · Issue 338616

Optimistic packaging updated to handle missing pxflows

Resolved in Pega Version 7.4

Opening a Work object on a Mobile device generated the error "The reference.pxFlow() is not valid. Reason: unexpected character ')' at position 8, expected subscript (wildcards not allowed)". This was traced to missing pxFlows due to the customized way the case was created, and handling has been added to clear the error messages in pyWorkPage while packaging for optimized cases.

SR-B82678 · Issue 338451

Optimistic packaging updated to handle missing pxflow errors

Resolved in Pega Version 7.4

Opening a Work object on a Mobile device generated the error "The reference.pxFlow() is not valid. Reason: unexpected character ')' at position 8, expected subscript (wildcards not allowed)". This was traced to missing pxFlows due to the customized way the case was created, and handling has been added to clear the error messages in pyWorkPage while packaging for optimized cases.

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