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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-130696 · Issue 199065

Updated config query for VBD date/time support

Resolved in Pega Version 7.1.8

When following the recommendation to add required date-time columns on VBD configuration tables for Oracle Golden Gate set up, the VBD configuration could not be saved to a database table from PRPC. This has been resolved by adding an updated configuration query to support replication.

SR-130713 · Issue 200675

getComputedStyle API issue in Microsoft Internet Explorer 8 resolved

Resolved in Pega Version 7.1.8

A JS error was appearing when using the Microsoft Internet Explorer 8 browser to complete the verification steps to submit a Smart Dispute, and clicking on the Submit button on the dispute screen showed no response. This was an issue with the updateHeaderCellsWidth API, and has been resolved.

SR-130731 · Issue 198828

HTTPS support added to DSM applications

Resolved in Pega Version 7.1.8

If the PRPC instance is accessed via HTTPS and the DSM applications (ADM & VBD) are installed on the same Tomcat configurations, the DSM services landing page did not provide the ability to say if the services were accessible via HTTPS. This is now possible through an added configuration option on the landing page to enable secure connection.

SR-130751 · Issue 198798

Clarified handling of unlocked work objects in multinode environments

Resolved in Pega Version 7.1.8

Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.

SR-130796 · Issue 197804

Enabled restore of persisted Application requestors

Resolved in Pega Version 7.1.8

Prior to this change, service requestors could not be restored from their passivated state because of a code change introduced in PRPC 5.4. This was generally not a problem for most customers, as service requestors tend to be stateless and short-lived. Stateful, long-lived service requestors such as Verizon do need to be restored to their previous state, however. This change retracts the prior fix that prevented that from occurring.

SR-130815 · Issue 199482

Updated API for 'Find' gadget

Resolved in Pega Version 7.1.8

The 'Find' gadget was not opening the existing WO in a new window as desired. This issue has been fixed by changing the strItemID location so that it will be passed to createFromEncryptedURL API.

SR-130959 · Issue 201417

Resolved stack overflow error on click close

Resolved in Pega Version 7.1.8

If a local action is configured on click of button in a section and a flow action is opened in the modal dialog, checking the option "Hide the default Action Section buttons?" in the action tab of flow action caused a stack overflow error when the X button was clicked to close the modal dialog. This has been fixed by adding a condition in focusOnModalDialogFirstElement to avoid refocusing on container_close when the modal does not have focusable elements.

SR-131124 · Issue 199831

Added enter key access to expand pane

Resolved in Pega Version 7.1.8

The expand pane icon in repeat grid was not accessible through enter key. This has been fixed.

SR-131136 · Issue 199333

Localization added for modal dialog alert boxes

Resolved in Pega Version 7.1.8

Localization has been added for modal dialog alert boxes.

SR-131176 · Issue 200691

Special character handling added to ShowHarness

Resolved in Pega Version 7.1.8

Previously, support was added to Decisioning -> Monitoring -> Adaptive Models Reporting for propositions beginning with special characters. An additional use case has been added to support the same in the activity 'uiactiondisplayharness' for ShowHarness.

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