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-114545 · Issue 164887

Increased limits for Bulk Processing

Resolved in Pega Version 7.1.7

When attempting to filter cases for Bulk Processing, the Property-List LookupList activity only requested a maximum of 2500 records. This caused an issue with class inheritance chains that contained more than 2500 property records, as those excess properties were not being used to filter within Bulk Processing area. To remedy this, the activity now allows a maximum of 10,000 records for Bulk Processing.

SR-114575 · Issue 168078

Search criteria passed to Report Definition

Resolved in Pega Version 7.1.7

The values entered in search criteria fields were not being passed to report definition, so the results were not shown in the Grid layout report. This was caused by an additional check on the classname of the parameters page while resolving filter values which are parameters, and has been resolved.

SR-114596 · Issue 164687

Check added for property with blank value

Resolved in Pega Version 7.1.7

If a property is left blank in the SelectTierOverride section, updating that section showed the message "'pega' is undefined" and a JavaScript error was generated. This was traced to the filePath control included in the section, which along with refreshing the section submitted filepath data to the server: if messages are set on page using Page-Set-Messages/Property-Set-Messages, then it will try to include pega_ui_textarea js file and fail. To correct this, a check has been added for blank properties.

SR-114670 · Issue 166258

JMS MDB listener updated to support JMS 1.1

Resolved in Pega Version 7.1.7

A compatibility issue with SonicMQ generated the error "Caused by: javax.jms.JMSException: [JMSPool:169823]Failure occurred on createQueueConnection" during initialization of the response connection. To remedy this, PRPC has been updated to support JMS 1.1.

SR-114670 · Issue 169790

JMS MDB listener updated to support JMS 1.1

Resolved in Pega Version 7.1.7

A compatibility issue with SonicMQ generated the error "Caused by: javax.jms.JMSException: [JMSPool:169823]Failure occurred on createQueueConnection" during initialization of the response connection. To remedy this, PRPC has been updated to support JMS 1.1.

SR-114673 · Issue 135949

Accessibility enhanced for keyboard access to accordion tabs

Resolved in Pega Version 7.1.7

With a design structure that has nested items, keyboard navigation was not shifting focus to the correct elements for nested items. Clicking with a mouse activated the nested item, then allowing use of the arrow keys to navigate, and tab could be used to move to the next item along with shift-tab to go back to the tab group. All items in the top Layout Group Accordion now correctly take focus and can be activated with keyboard arrow keys. Tabbing from the active accordion takes the focus into the content of the active element within the accordion.

SR-114673 · Issue 139984

Accessibility enhanced for keyboard access to accordion tabs

Resolved in Pega Version 7.1.7

With a design structure that has nested items, keyboard navigation was not shifting focus to the correct elements for nested items. Clicking with a mouse activated the nested item, then allowing use of the arrow keys to navigate, and tab could be used to move to the next item along with shift-tab to go back to the tab group. All items in the top Layout Group Accordion now correctly take focus and can be activated with keyboard arrow keys. Tabbing from the active accordion takes the focus into the content of the active element within the accordion.

SR-114673 · Issue 140386

Accessibility enhanced for keyboard access to accordion tabs

Resolved in Pega Version 7.1.7

With a design structure that has nested items, keyboard navigation was not shifting focus to the correct elements for nested items. Clicking with a mouse activated the nested item, then allowing use of the arrow keys to navigate, and tab could be used to move to the next item along with shift-tab to go back to the tab group. All items in the top Layout Group Accordion now correctly take focus and can be activated with keyboard arrow keys. Tabbing from the active accordion takes the focus into the content of the active element within the accordion.

SR-114673 · Issue 170001

Accessibility enhanced for keyboard access to accordion tabs

Resolved in Pega Version 7.1.7

With a design structure that has nested items, keyboard navigation was not shifting focus to the correct elements for nested items. Clicking with a mouse activated the nested item, then allowing use of the arrow keys to navigate, and tab could be used to move to the next item along with shift-tab to go back to the tab group. All items in the top Layout Group Accordion now correctly take focus and can be activated with keyboard arrow keys. Tabbing from the active accordion takes the focus into the content of the active element within the accordion.

SR-114690 · Issue 169172

Space no longer reserved in the header for hidden custom icons

Resolved in Pega Version 7.1.7

After upgrading, custom icons hidden based on visibility conditions were presenting as empty occupied space in the perform screen flow harness instead of allowing the other icons to consolidate as expected. This was caused by the cell of the harness header icon remaining in place even though the icon was not being populated, and has been corrected.

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