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-A7590 · Issue 216110

Corrected parameter page used when Flowproblems restarts

Resolved in Pega Version 7.2

Restarting the problem flow was not taking the mandatory parameters defined in the flow, instead generating the error "Required parameter Parameter_name." To correct this, the flow method body has been modified to populate the parameter page from the pyFlowParameters page before checking for mandatory parameters.

SR-A10189 · Issue 222038

Handling added to set baseclass when using Bulk as Update

Resolved in Pega Version 7.2

The use case was missing to properly handle setting the baseclass when Bulk action was selected as an Update process. This has been added.

INC-175630 · Issue 653863

Application selections only announced when visible

Resolved in Pega Version 8.7

The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.

SR-130442 · Issue 212468

Added support for localization of the 'Advanced' value of the When rule

Resolved in Pega Version 7.2

If the "Advanced" value was localized in the When rule form, it failed as it was trying to compare with localized text. To resolve this, WhenTabListener has been modified to use the ID attribute instead of text for comparison.

SR-A12587 · Issue 224456

Added support for localization of the 'Advanced' value of the When rule

Resolved in Pega Version 7.2

If the "Advanced" value was localized in the When rule form, it failed as it was trying to compare with localized text. To resolve this, WhenTabListener has been modified to use the ID attribute instead of text for comparison.

SR-B95830 · Issue 344260

Better handling for case updating when switching applications

Resolved in Pega Version 7.4

When using two applications, the application 1 case lifecycle view was shown at login. After switching to application 2, the case life cycle was not updated until the refresh icon was clicked. This was an issue with the pyCurrentCase value not being updated while switching apps, and an additional condition has been added to the pzSetCurrentCase Data transform to better handle application switching.

SR-B82049 · Issue 341054

pxCoverInsKey set in audit history when childcase created

Resolved in Pega Version 7.4

On adding an audit note during the creation of the child case, the audit history did not contain the reference to the parent case. Eventually, when the case was referenced, the pxCoverInsKey was populated in the history table. This was caused by an ordering error in the logic and the system has been updated to correct it.

INC-143861 · Issue 597557

pzIsScalar 'when' rule updated for Value list and Value group

Resolved in Pega Version 8.5.2

When using the GET/Cases/{ID} API to fetch details about a case, an intermittent HTTP 500 error appeared. This was traced to the 'when' condition pzIsScalar being returned as true for the ValueList property types and trying to set the value on the summaryData embedded page. This has been resolved by updating the pzIsScalar 'when' rule to better handle Value list and Value group.

SR-A6363 · Issue 216182

Resolved Where AM I issue when there is flow on embedded page

Resolved in Pega Version 7.2

Clicking on the "Where Am I?" option when there was a subprocess defined on embedded page in a flow failed to display anything on screen and an error was logged. This was caused by the obj-open referring to the wrong flow class value, and has been corrected.

SR-A9389 · Issue 219242

File name truncation used for File Listener recovery

Resolved in Pega Version 7.2

The Property Data-WorkAttach-.pyNote default of Max Length = 60 caused a failure in File Listener's recovery mode if the system added a long string at the end of the file name. This has been fixed by trimming and setting pyNote if the length is more then 60 characters.

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