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-123056 · Issue 186144

FCM IAC caching improvements

Resolved in Pega Version 7.1.8

Analysis on the web server access logs found that content such as JS, image, and CSS files are cached correctly when accessing PRPC directly but not cached at all on the client when the same case is opened via the FCM IAC Gateway. This caused network congestion for the browser. To resolve this, the system now removes the appending forward slash from the thread name in the finalizeNavURL method when the request is issued to a gateway, allowing the download of the static content based on the application instead of the thread name.

SR-123056 · Issue 185070

FCM IAC caching improvements

Resolved in Pega Version 7.1.8

Analysis on the web server access logs found that content such as JS, image, and CSS files are cached correctly when accessing PRPC directly but not cached at all on the client when the same case is opened via the FCM IAC Gateway. This caused network congestion for the browser. To resolve this, the system now removes the appending forward slash from the thread name in the finalizeNavURL method when the request is issued to a gateway, allowing the download of the static content based on the application instead of the thread name.

SR-123076 · Issue 186001

Resolved update script error for indexes

Resolved in Pega Version 7.1.8

An update script encountered an error when trying to drop an index, PR4_RULE_VW_PK. This was caused by the DDL being split when an upgrade is being performed, with all drop statements being executed first and then the rest of the statements are run. This changes the order that the DDL needs to run in for changing primary keys, where the table needs to be altered to drop the constraint first, and then have the index dropped. To fix this, all "drop constraints" have been moved to the start, followed by "drops" and "alter" DDLs.

SR-123095 · Issue 184829

Removed redundant save prompt for changed logging levels

Resolved in Pega Version 7.1.8

When a logging level in Designer Studio was changed, a prompt appeared to save the rules upon exiting the System operations page. This was redundant - the log level is saved immediately when it is changed in the modal dialogue "Logging Level Settings", and the extra prompt has been removed.

SR-123106 · Issue 188198

Scroll bar corrected in tabbed work areas with tree grids

Resolved in Pega Version 7.1.8

If a section with tree grid is configured in a tabbed Work Area and has a vertical scroll bar, expanding the node of the tree grid caused the scroll bar to disappear. Clicking on the same node brought the vertical scroll bar back. The issue was in the resizeCallback function of the PegaCompositeGadgetMgr JS file. The overflowY attribute of the workarea gadget div has been set to 'auto' to avoid this behavior.

SR-123127 · Issue 185219

Improve error handling for File Listener

Resolved in Pega Version 7.1.8

The File Listener not processing all files successfully when there was more than one file to be processed. This was caused by missing logic for the clearing of 'hasOnce' at the file level for the record type. Since 'hasonce' was not cleared at file level, once a file with an incorrect configuration is processed, others files were also getting processed as errors. This has been resolved by adding code to reset the 'hasonce' on a per file basis so File Listener is able to process multiple files.

SR-123130 · Issue 184202

Added apostrophe handling for navigation rule item names

Resolved in Pega Version 7.1.8

If an apostrophe (') was present in the label of Navigation rule item name, the onclick functionality of menu option was not working and threw a JavaScript error. In this JS file, the eval(strAction) function call failed because strAction text contains all the parameters enclosed in single quotes: if the label contains an apostrophe, that became an extra quote in this text. To avoid this, the functions pzMenuBarTranslator and pzActionShowHarness have been modified to handle extra apostrophes passed by the label.

SR-123136 · Issue 182969

Corrected Worklist filtering for dynamic Repeat Grids

Resolved in Pega Version 7.1.8

Worklist filtering was not working for columns added to the Repeat Grid dynamically using virtual report definition. This was a functionality gap in handling show/hide and filtering on dynamic columns virtual RD bound grid, and has been fixed.

SR-123149 · Issue 184289

SOAPRequestEnvelope parameter added for custom Auth Activity

Resolved in Pega Version 7.1.8

In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".

SR-123149 · Issue 186790

SOAPRequestEnvelope parameter added for custom Auth Activity

Resolved in Pega Version 7.1.8

In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".

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