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-C39546 · Issue 383651

Listeners added to explicitly unload windows to resolve OpenURLInWindow memory leak

Resolved in Pega Version 8.1

Opening another domain URL's using the "openURLInWindow" API was causing a memory leak. This was traced to the beforeunload listener not being triggered by the browser, as it is a cross-site security issue. To resolve the leak, the system will handle cross domain windows by holding the window name instead of an object and ensuring it is closed during the window unload. For same domain windows, listeners have been put in place to add it to opened windows during onload and then remove it during window unload events.

INC-162649 · Issue 639400

DSS added for handling missing attachments

Resolved in Pega Version 8.7

When an S3 repository was configured as storage, some cases were not coming up in search and exception errors were seen in logs for a deleted attachment after every system restart/re-indexing of the search. Investigation showed these case objects were in the broken queue for pyFTSIncrementalIndexer due to a null pointer error encountered when indexing the attachment, and that the attachments were available in the repository but could not be read from the attachment repository during indexing. To resolve this, a new DSS setting has been added which allows selecting one of two behaviors: * Pega-SearchEngine indexing/distributed/fail_on_missing_attachment_file = true : broken item is generated, but with a meaningful error message. This is the default behavior * Pega-SearchEngine indexing/distributed/fail_on_missing_attachment_file = false: case is indexed, but without the problematic attachment. Error message is printed out to the logs.

INC-144917 · Issue 598200

Healthcheck will only initialize after successful node startup

Resolved in Pega Version 8.5.2

Nodes were not starting up, but because the Healthcheck service was initialized even though the node was not started properly, errors related to that were overriding the actual exception causing the node startup to fail and it was not possible to diagnose the startup issue. To resolve this, an update has been made that will ensure the Healthcheck service is only initialized when the node is initialized successfully.

SR-C27659 · Issue 368116

Modified survey logic for modal dialog radio button rendering

Resolved in Pega Version 8.1

When Survey was rendered on a modal dialog, radio button questions were not getting displayed. This was traced to the system skipping some stream generation logic due to a purpose called VALIDATE which was set incorrectly in post processing. To resolve this, the code for validation at the question level has been moved below the stream generation logic in the SurveyAccessMethodBodyQuestionCollection and SurveyAccessMethodBodyQuestion FUAs.

SR-C29307 · Issue 369458

Reference tracker tracks references to the page list properties in non-auto-generated sections

Resolved in Pega Version 8.1

In certain cases reference tracker would miss complex property references, especially when a primary page had nested embedded pages and page lists. This has been resolved by changing the underlying reference tracker implementation to be independent from the page structure. The new implementation is more robust and 100% compatible with DSM clipboard pages.

SR-C6595 · Issue 351217

Handling added for empty Dropdown placeholders

Resolved in Pega Version 8.1

When a field value was referred for a place holder of a autocomplete, at runtime it varied whether the place holder or the property name was displayed. This was traced to the handling for an empty currentContext.getLocalizedValue; the actual value was being passed if there is no corresponding entry in the context tree. The system has now been modified to avoid a call to the pega.clientTools.getLocalizedTextForString API if the property name value is empty.

INC-190819 · Issue 681999

Wrapper added to set correct bulk transfer context

Resolved in Pega Version 8.7

Bulk transfer was not working as expected when transferring an assignment from a flow defined in data class. Investigation showed the bulk transfer UI was getting picked from work- class while the post processing was running under data class context: this has been resolved by creating a wrapper activity in baseclass to call the post processing activity Work- .

INC-179722 · Issue 659280

Added handling for legacy HTML formatting in Email Manager Bot

Resolved in Pega Version 8.7

When implementing Email Manager Bot features, pyBody fields were removing the additional spaces and causing the NLP model to not extract the correct data. Investigation showed HTML formatting from older version of Microsoft Outlook created nbsp; instead of space. This has been resolved by ensuring nbsp is replaced with spaces before calling JSoup clean.

INC-198632 · Issue 687582

Handling added to correct class setting during DX-API

Resolved in Pega Version 8.7

When a DX-API call was made (assignments/{ID}/actions/{actionID}/refresh) the ApplyPageInstructions activity was updating the case with an incorrect class, causing the rules from the wrong class to be picked and blocking the case progression. This has been resolved by setting the proper parameter Param.workPage while calling pzApplyPageInstructions from pzUpdateCaseWithRequestBody to calculate the proper class for the content.

INC-178214 · Issue 664890

D_ProjectList updated to resolve defined databases error

Resolved in Pega Version 8.7

After update, an API error for D_ProjectList indicating "No databases defined" was seen when trying to load decision and templates for the first time. The error did not reoccur after the initial save. This was has been resolved by updating the handling for loading the properties file during class loading. The error has also been changed to an exception.

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