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-117204 · Issue 168225

Error message logging improved for DB2

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

During normal development activities, a console log was showing a large volume of Integrity Constraint Violation Exceptions that seemed to correlate with the level of activity of users and the number of concurrent active users. The system uses infoForced to make sure "real" errors are reported, but attempts to suppress those deemed to be "noise". In this case, the system was lacking an additional "if" test for DB2, and this has been added.

SR-117205 · Issue 171200

Corrected datetime calendar validation on forms with messages

Resolved in Pega Version 7.1.7

When messages were present on a form (validation, etc.) and the date selector was used, the screen blanked after selecting the date. This was caused by an error in the datetime calendar popover and has been resolved.

SR-117216 · Issue 168600

Validation corrected for Case Manager portal types

Resolved in Pega Version 7.1.7

After migration, changing the application header text for the Case Manager portal was throwing the error "pySkinType: ** You must specify a skin to use or select "Default to Application Skin" upon checkout. To correct this, the validation activity step has been updated with a 'when' expression to skip this validation for mobile portals

SR-117228 · Issue 168249

Resolved issues with Flow shapes distributed across Swim Lanes

Resolved in Pega Version 7.1.7

Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.

SR-117252 · Issue 174014

Modified SaveAs function for reports to avoid duplication

Resolved in Pega Version 7.1.7

After using "SaveAs" on an existing report, subsequently using "Save" caused two instances of the report to be saved into the database with the same key. The SaveAs function has been modified to correct this.

SR-117255 · Issue 174772

Required fields corrected for repeating grids in accessibility mode

Resolved in Pega Version 7.1.7

When using a repeat grid with required fields in accessibility mode, the field displayed multiple asterisk symbols instead of one. This problem was with workform_accessibility.CSS, and was resolved by changing the background image url to "transparent". The "REQUIRED" text was also not showing with IE8: this was noticed only in IE8 Standards mode, and an accessibility check was added to generate the span containing REQUIRED text in the html stream.

SR-117265 · Issue 169903

Clarified "time" display for Calendar

Resolved in Pega Version 7.1.7

While using "pxCalendar" section to display task time, '?' was displayed near the current time in Daily and Weekly view. To avoid confusion, the '?' symbol has been replaced with the text 'Time' in a field value, which can be overridden accordingly.

SR-117265 · Issue 170246

Clarified "time" display for Calendar

Resolved in Pega Version 7.1.7

While using "pxCalendar" section to display task time, '?' was displayed near the current time in Daily and Weekly view. To avoid confusion, the '?' symbol has been replaced with the text 'Time' in a field value, which can be overridden accordingly.

SR-117266 · Issue 173481

Prompt Select modified to properly handle XSS functions

Resolved in Pega Version 7.1.7

A selection made in Prompt Select was not retained after refresh when special characters were present in the selected value. This was caused by XSS filtering functions that compared an encrypted value with the prompt value and negated it when it wasn't equal. To fix this, PromptSelect has been modified to call the crossScriptingFilter API before appending strDefaultValue to the stream.

SR-117307 · Issue 171895

Improved submit flow for better accessibility with JAWS

Resolved in Pega Version 7.1.7

When the Create or Submit button on a flow action is clicked, dismissing the "You are about to change the current window" popup would sometimes cause JAWS to read extraneous messages such as "Create button unavailable" and "Main region end". This behavior was sporadic and depended on how quickly the popup was dismissed. In order to avoid this, the button function calls have been modified.

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