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-C62425 · Issue 401586

oLog.infoForced has been replaced with oLog.debug in GetAssignmentDetailsInternal to reduce excessive logging

Resolved in Pega Version 8.2

The Rest API used by Robotics was generating excessive logging on the application server due toPzGetAssignmentDetailsInternal generating several lines of logs with each REST call. In a high volume system, this can make the logs difficult to utilize. To resolve this, oLog.infoForced has been replaced with oLog.debug.

SR-C62573 · Issue 405925

Test case data purge made configurable to improve rule opening performance

Resolved in Pega Version 8.2

Slowness when opening rules like Decision tree, flows, and decision tables was traced to some rule form test cases data being automatically loaded during opening. This has been addressed by modifying the "pzPergeTestResultsData" activity to read the value from "pegaunit/purgeAgeInDaysForTestResults" DSS to delete the test results records from the database based on the purge age. The default is 180 days.

SR-C70724 · Issue 408367

Test case data purge made configurable to improve rule opening performance

Resolved in Pega Version 8.2

Slowness when opening rules like Decision tree, flows, and decision tables was traced to some rule form test cases data being automatically loaded during opening. This has been addressed by modifying the "pzPergeTestResultsData" activity to read the value from "pegaunit/purgeAgeInDaysForTestResults" DSS to delete the test results records from the database based on the purge age. The default is 180 days.

SR-C71877 · Issue 411406

OperatorSkillCountint calculation corrected

Resolved in Pega Version 8.2

The pxOperatorSkillCountInt in the operator profile was increasing each time GetNextWork was run. This was caused by a calculation error, and has been corrected by resetting .pxOperatorSkillsCount value every time SetWorkInfo is invoked.

SR-C55309 · Issue 393858

OperatorSkillCountint calculation corrected

Resolved in Pega Version 8.2

The pxOperatorSkillCountInt in the operator profile was increasing each time GetNextWork was run. This was caused by a calculation error, and has been corrected by resetting .pxOperatorSkillsCount value every time SetWorkInfo is invoked.

SR-C69948 · Issue 414251

Corrected JSON for eventType DisableOperators in the security event log

Resolved in Pega Version 8.2

An event entry in PegaRULES-SecurityEvent.log was generating invalid JSON. This was traced to eventType DisableOperators (not disable operators) containing a message attribute with unescaped double quote characters surrounding the operator names. This has been fixed.

SR-C75056 · Issue 414109

Corrected JSON for eventType DisableOperators in the security event log

Resolved in Pega Version 8.2

An event entry in PegaRULES-SecurityEvent.log was generating invalid JSON. This was traced to eventType DisableOperators (not disable operators) containing a message attribute with unescaped double quote characters surrounding the operator names. This has been fixed.

SR-C80753 · Issue 419246

Native calendar control works for Firefox on Android

Resolved in Pega Version 8.2

When using Firefox with 'Use native control on mobile' checked, attempting to enter a date into the DateTime field highlighted the mm field but the date selector did not open and keyboard entry was not recognized. This was traced to the native calendar for date time control not opening in Firefox on Android. To correct this, type checks for date, time and datetime-local have been added to the isTextBox function in pzpega_ui_events_infra js.

SR-C62820 · Issue 404256

Fixed dropdown value reset on Microsoft Edge 41 browser

Resolved in Pega Version 8.2

When using the Microso9ft Edge 41 browser, any value selected in a dropdown was getting reset to the placeholder. Also, if there was a dropdown with required validation, then after the selection was made a reset happened and fired a validation message. This was traced to the selectedIndex of dropdown not getting updated properly in Edge if the option was added dynamically with selected attribute, and has been fixed by setting selectedIndex to dropdown in constructOptions function of pzpega_ui_dropdown.js.

SR-C56980 · Issue 399535

Validation corrected to honor Read-Only designations

Resolved in Pega Version 8.2

Validation was happening on Read-Only fields due to pyReadonlyValidation not being honored in all editable cases. This 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