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-192464 · Issue 681751

PackageComponent updated for use with repositories

Resolved in Pega Version 8.7

Exporting a zip file created by the Component wizard to a repository resulted in an error, however the same process worked as expected when the zip file was created by the Product wizard. Investigation showed that pxPackageComponent was not kept up to date with new metadata requirements for Artifactory export. This has been resolved by modifying pxPackageComponent step 7 to set Param.ArtifactType to "component" and Param.ArtifactName to [component name]_[component version]. A privilege check has also been added to zipMoveExport.

SR-C1026 · Issue 344634

Able to add When condition for DisplayYesNo

Resolved in Pega Version 7.4

An exception was generated when attempting to add 'when' conditions for DisplayYesNo control in Section. The pzActionConditionSource activity was fetching the pyUIElement value from the Primary Page and setting it to UIELement as intended, but when the pyUIElement value is empty, a null-pointer exception occurs. Handling has now been added to avoid this scenario.

SR-B68991 · Issue 336840

Fixed Expand when evaluation for nested RDLs

Resolved in Pega Version 7.4

When using a nested repeating dynamic layouts that included section with collapsible headers, using a property pyExpanded and a custom 'when' rule isExpanded to expand and collapse the layouts and refresh the parent section from deep within the nesting was sporadically producing unexpected results. If the pagination was set on the inner RDL, after refresh the layouts were not always in the same "expanded" state as they were before the refresh. This was traced to a unique ID not being generated for the expand-indicator inside progressive loaded RDL, and has been fixed.

INC-196414 · Issue 684238

OAuth token refreshed when revoked on source

Resolved in Pega Version 8.7

When an OAuth token was used to authorize the APIs in the system, revoking the token at the source, i.e. from the Service side, did not automatically refresh the token and a logoff/logon was required before a fresh token was generated. This has been resolved by adding an update to explicitly purge revoked tokens.

SR-B70521 · Issue 340527

Accordion stays in view when changing tabs

Resolved in Pega Version 7.4

The content in the accordion group was scrolling down below/above the screen frame when other layouts were selected. This was an issue with the accordion not being in viewport when opened since the content was hidden using display:none, and has been fixed by calling scrollIntoViewIfOutOfView for active accordion. ScrollIntoViewIfOutOfView is defined in pzpega_ui_doc_domUtils.

INC-178417 · Issue 670114

Flag reset added for grid with 'Expand When'

Resolved in Pega Version 8.7

A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.

SR-B95350 · Issue 341577

Rollbacks use CreateDateTime for ordering list

Resolved in Pega Version 7.4

When processing a rollback for multiple hotfixes, the system was retrieving a list of uncommitted hotfixes from the database without specifying any order and, as a result sometimes the item were in the correct (i.e. reverse of installed) order and sometimes not. This was the unintended consequence of switching to using generated unique IDs which do not maintain any ordering, and has been fixed by modifying the process of retrieving the uncommitted hotfixes list to provide descending ordering based on pxCreateDateTime.

SR-B94720 · Issue 342356

Fixed disable when on button with two expressions

Resolved in Pega Version 7.4

When selecting Visibility condition (when Rule) and Disable Condition (expression) and adding two expressions, the second one failed with an "Invalid property reference" error and the Save button was disabled. Attempting to remove the 2nd expression still resulted in the Save button still being disabled due to the clipboard continuing to hold the incorrect entered value. Closing the expression outside the modal window and reopening it enabled the Save Changes button. This behavior was due to incorrect validation resulting from the lack of a 'when' check in pzValidateExpressionDialog for the secondLeftOperand, and this check 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-D39302 · Issue 507981

Report name in tab uses localization

Resolved in Pega Version 8.2.4

After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.

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