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-114896 · Issue 168564

ActionAutoSubmit HTML rule corrected

Resolved in Pega Version 7.1.7

A flaw in the ActionAutoSubmit function caused it to require manual submission once all files were loaded. This has been corrected.

SR-114898 · Issue 167508

Radio button focus corrected

Resolved in Pega Version 7.1.7

Focus was not being properly set for radio buttons, including a scenario where a section refresh on click of a radio button moved the focus to the first element within the radio button group instead of to the radio element which was clicked. This was traced to missing logic for the radio buttons, and has been fixed.

SR-114913 · Issue 165658

Corrected error message display for dynamic layouts

Resolved in Pega Version 7.1.7

Multiple validate error messages for a particular field in a dynamic layout were displaying on the same line at run time and appearing as a single error message text. This was caused by error messages being directly appended, and has been changed to display each error as separate string in every span.

SR-114917 · Issue 166117

Alignment issues with IAC resolved

Resolved in Pega Version 7.1.7

When a dynamic layout of stacked style was used in conjunction with IAC, resizing the window caused the elements to not be properly aligned. CSS issues in the HTML handling of overflow properties have been corrected with the resizing harnesses.

SR-118050 · Issue 169612

Alignment issues with IAC resolved

Resolved in Pega Version 7.1.7

When a dynamic layout of stacked style was used in conjunction with IAC, resizing the window caused the elements to not be properly aligned. CSS issues in the HTML handling of overflow properties have been corrected with the resizing harnesses.

SR-115104 · Issue 165556

IAC functionality enhanced for secure environments

Resolved in Pega Version 7.1.7

In order to ensure IAC functionality in a secure environment, the following updates were made: HTTPOnly support has been enabled for prGatewaySESSIONID cookies; encryption and obfuscation have been set up for web nodes; added a check for login-config.xml to add default-users.properties and default-roles.properties to the other application-policy.

SR-115242 · Issue 164582

Last row delete in Grid Repeat generated an error

Resolved in Pega Version 7.1.7

If a Grid Repeat contains only one row, hitting 'delete' properly removed the row, but the java script error "this.rightBodyTbl.rows[...].cells is null or not an object" appeared. This error was caused by a missing null check inside the focusing api, and has been fixed.

SR-115272 · Issue 167336

Corrected clipboard mismatch for refreshed Repeating Grid pages

Resolved in Pega Version 7.1.7

When using Repeating Grid pagination in Screen Flow, refreshing the screen by choosing that option from the context menu displayed with a right-click followed by selecting 'Next' on the repeat grid caused a NPE. This was caused by a mismatch with the clipboard page, and has been corrected.

SR-115387 · Issue 166507

Flow Action support tuned for MenuBar keyboard navigation

Resolved in Pega Version 7.1.7

Using the' MenuBar' setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu: the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouse click was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected.

SR-115392 · Issue 164192

Added customization for PDF page numbers

Resolved in Pega Version 7.1.7

Previously, it was not possible to designate the initial page number in the PDF generated by HTMLToPDF activity. Two parameters have been added to allow for greater customization: "header" activates page number support in the document header, and "startPage" is used to set the initial page number for the document. The "startPage" parameter can be used for both the header and footer.

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