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-D42602 · Issue 511583

PRCipher class references updated

Resolved in Pega Version 8.3.1

After upgrade, starting Tomcat resulted in the error "java.lang.ClassCastException: com.pega.platform.securitycore.encryption.internal.CipherDefault cannot be cast to com.pega.pegarules.exec.external.util.crypto.PRCipher"This was traced to an issue with the references for PRCipher: cipher was moved to be a security-core component, but the class structure changes were not fully updated. This has been corrected.

SR-D44307 · Issue 509000

Refined dependency checking for Hotfix Manager

Resolved in Pega Version 8.3.1

The logic in Hotfix Manager was changed in 8.3 to include all Strategic Application hotfixes in the Catalog for platform versions 7.4+. However, because there are some edge cases where multiple hotfixes for different strategic application products have been shipped with the same rule changes, it was found that a DL packaged for one application could pick up hotfixes intended for another app. This prevented the DL from installing on systems where both apps were not installed. To avoid picking up these additional hotfixes, while the catalog shipped in the DL will continue to contain all apps, the system has been updated to use only a list of selected products when generating a catalog for calculating dependencies.

SR-D23164 · Issue 493795

Edit icon removed from deprecated custom skin styling

Resolved in Pega Version 8.3.1

Using custom styles as skin component is a deprecated feature as of Pega Platform v8.2. While existing styles will still be added to the CSS file when upgrading to or beyond this version, adding or updating custom skin styles is now handled through manual CSS files included in the skin. As part of this change, the edit icon for changing custom styles has been removed.

SR-D30944 · Issue 503231

Corrected pagination alignment in tabbed layout sourced from RD

Resolved in Pega Version 8.3.1

Pagination numbers were not being presented inline with the next/back arrows when using a tabbed table layout with source:report definition. To resolve this, the pyGridPaginator function has been added to Pega-Gadgets in Work- .

SR-D19083 · Issue 490402

Autocomplete list resets to top of scroll if selected data is deleted from the control

Resolved in Pega Version 8.3.1

If an autocomplete on Screen did not initially have any input, pressing the down arrow showed the popover data with the scrollbar on the top. Scrolling down and selecting an item from the autocomplete suggestions and then tabbing out closed the popover. If the data was then deleted from the control and the down arrow was pressed again, the popover suggestion showed the data in the last scrolled position instead of restarting from the top as expected. Investigation showed that when autocomplete used a list configuration, the popover div was not being updated if the data was deleted from the control. This has been corrected.

SR-D15844 · Issue 496775

Flag set for using defer load context switching with Microsoft Internet Explorer

Resolved in Pega Version 8.3.1

Defer load section was not working as expected due to Microsoft Internet Explorer 11 not maintaining the context of the section during busyIndicator hide. To avoid this, a flag 'pega.ctxmgr.skipContextSwitching' will be set during the hide of busy indicator if Microsoft Internet Explorer is used, and the harness switching context will then be decided based on this flag.

SR-D17568 · Issue 498409

Handling added for interaction portal refresh containing many data parameters

Resolved in Pega Version 8.3.1

Attempting to refresh the browser when there were interactions opened in the Interaction portal and a huge amount of data on the parameter page caused the screen to blank and the interaction content was not displayed. Investigation showed that as part of the refresh, the displayOnPage GET request was sent with all of the parameters in the parameter page (data-model), resulting in a 400 Bad Request due to the browser URL length limitations. This has been resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case.

SR-D18960 · Issue 499909

Logic updated to resolve busy indicator delay

Resolved in Pega Version 8.3.1

On click of submit in the main interaction flow, the busy indicator was not getting displayed or was displayed after a delay whenever there were a series of Ajax requests being made. The logic has been updated to resolve this issue.

SR-D19177 · Issue 492338

Mashup refined to not trigger resize from popup

Resolved in Pega Version 8.3.1

The parent window was being refreshed when an action was performed on the child window or the child window was resized from the mashup script. This has been resolved by altering the logic to avoid triggering resize from popups in a mashup scenario.

SR-D19801 · Issue 495838

Corrected embedded section inside dynamic layout group becoming read-only

Resolved in Pega Version 8.3.1

When using a nested sections structure in a Dynamic Layout Group (tab), the fields inside the layout group were becoming read-only. This has been resolved by ensuring the controls present in second-level nesting onwards obey section read-only value in a dynamic layout group, and resolving the 'when' rule that governs the disabledwhen of link for all sections in a section include.

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