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-123008 · Issue 185495

Improved performance for heavily active ruleset grids

Resolved in Pega Version 7.1.8

Progressive performance issues were seen in environments with frequent rule updates. Memory leaks were found in the grid code, and performance has been enhanced by the following updates: An erroneous global object was removed and the process tuned for nullifying the grid objects. The Section RuleFormLayout rule had the DesignViewInclude section was erroneously included twice: the duplicate has been removed. Issues were resolved in the "openRuleAdvanced," tab support, and dynamic container controls. An event listener has improved handling of load and unload of the menus. Av condition was added in if block checking for styleClass which adds correct number of dots for the case where image source selected is icon class. The Actions split button was consolidated to a single button with a down arrow. The +Create submenu was removed from the actions menu for @baseclass and 3 overrides. The autoAdjustProgressiveGrid was optimized. Handling for Composite Gadget manager was updated.

SR-123008 · Issue 190908

Improved performance for heavily active ruleset grids

Resolved in Pega Version 7.1.8

Progressive performance issues were seen in environments with frequent rule updates. Memory leaks were found in the grid code, and performance has been enhanced by the following updates: An erroneous global object was removed and the process tuned for nullifying the grid objects. The Section RuleFormLayout rule had the DesignViewInclude section was erroneously included twice: the duplicate has been removed. Issues were resolved in the "openRuleAdvanced," tab support, and dynamic container controls. An event listener has improved handling of load and unload of the menus. Av condition was added in if block checking for styleClass which adds correct number of dots for the case where image source selected is icon class. The Actions split button was consolidated to a single button with a down arrow. The +Create submenu was removed from the actions menu for @baseclass and 3 overrides. The autoAdjustProgressiveGrid was optimized. Handling for Composite Gadget manager was updated.

SR-123008 · Issue 185492

Improved performance for heavily active ruleset grids

Resolved in Pega Version 7.1.8

Progressive performance issues were seen in environments with frequent rule updates. Memory leaks were found in the grid code, and performance has been enhanced by the following updates: An erroneous global object was removed and the process tuned for nullifying the grid objects. The Section RuleFormLayout rule had the DesignViewInclude section was erroneously included twice: the duplicate has been removed. Issues were resolved in the "openRuleAdvanced," tab support, and dynamic container controls. An event listener has improved handling of load and unload of the menus. Av condition was added in if block checking for styleClass which adds correct number of dots for the case where image source selected is icon class. The Actions split button was consolidated to a single button with a down arrow. The +Create submenu was removed from the actions menu for @baseclass and 3 overrides. The autoAdjustProgressiveGrid was optimized. Handling for Composite Gadget manager was updated.

SR-123011 · Issue 182646

Added null check for datetime in SOAP

Resolved in Pega Version 7.1.8

Some SOAP services using a Response Parameter with Data Type of DateTime and for services of type RPC/ literal were generating an NPE when the service was executed outside Pega7 using Google Chrome. Running the service directly from the service rule within Pega7 did not encounter this error. Other SOAP requests returned a date of 1970-01-01. This was traced to a check to get the thread which did not handle situations where PRDateFormat.formatXSDDateTime() could be null, and the handling for that case has been added for this browser.

SR-123018 · Issue 183818

Addressed ruleset integrations problems using Google Chrome

Resolved in Pega Version 7.1.8

When using Google Chrome and running the Integration > Tools > Rule-From-File wizard, the ruleset version was not displayed and it was not possible to proceed past the screen that requires values for rule name, ruleset, ruleset version and class name. This was due to there not being an input field for RuleSet Version, and the validation of that step in the wizard fails. This issue occurred due to Google Chrome not supporting the use of document.all in the HTML code, leading to an undefined value for the JavaScript. This has been resolved by changes to the HTML to make it browser code independent.

SR-123023 · Issue 185999

Fixed emailing error for Report Browser subscriptions

Resolved in Pega Version 7.1.8

Once someone is subscribed to a scheduled report created in Report Browser, an email should be sent based on task scheduling. This was not happening as expected, though the status in the scheduled tasks was showing as sucessful. This was caused by an error in the ActionSendMailReporting activity which set the FromUserName to EmailAccount.pyEmailAddress instead of EmailAccount.pySMTPUserName, and has been corrected.

SR-123031 · Issue 182673

Corrected inheritance logic for ComputeSegment

Resolved in Pega Version 7.1.8

ComputeSegmentLogic activity logic was not considering inheritance path. This was an issue with having the run-time rule resolution at design-time, and has been changed to pass propagate the apply-to class to sub-activity calls so that it can pick up the right rule.

SR-123044 · Issue 182684

Improved failure handling for cache loading on startup

Resolved in Pega Version 7.1.8

During server startup after upgrade, a data page with a failed definition cache prevented all remaining data page definitions from loading into the cache. This was found to be caused by a Node scoped data page which had only shared rule sets and did not have at least one production ruleset. In order to smooth startup, the declarative data page definition cache load will skip one particular improper record if found and continue processing.

SR-123051 · Issue 182680

LogOut' function corrected in the out-of-the-box operator menu

Resolved in Pega Version 7.1.8

When using the out-of-the-box provided "pyCaseMgrOperatorMenu" navigation rule, the menu contains two items - 'Preference's and 'LogOut'. Clicking on 'Log Out' was not performing log out operation. This was an error in the logout item of the navigation rule PYCASEMGROPERATORMENU, which was using an old script. This has been replaced with the new out-of-the-box logoff action.

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.

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