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-116769 · Issue 174513

Case narrative ordering enhanced

Resolved in Pega Version 7.1.7

The Case Narrative ordering appeared incorrectly when the events are very close together (multiple events within the same second), though the History items displayed in the correct and expected order. When more than one event occurred within the same second, the DATE datatype did not provide a lower level of distinction to allow more granular sorting or ordering. To resolve this, the time value for sorting is now extracted from InsKey.

SR-116893 · Issue 169075

Corrected browser display errors for large decision tables

Resolved in Pega Version 7.1.7

A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.

SR-117937 · Issue 173922

Corrected browser display errors for large decision tables

Resolved in Pega Version 7.1.7

A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.

SR-116908 · Issue 168347

When rules now display all text fields for function aliases

Resolved in Pega Version 7.1.7

Creating a new Access When rule failed to show the text fields for most available function aliases when a condition was added to the rule. This was an error in the passing of the classname to the function, and has been fixed.

SR-116950 · Issue 167458

Rule name validation checks relaxed for draft mode

Resolved in Pega Version 7.1.7

In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.

SR-116950 · Issue 168328

Rule name validation checks relaxed for draft mode

Resolved in Pega Version 7.1.7

In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.

SR-117164 · Issue 169821

Tightened vertical privileges

Resolved in Pega Version 7.1.7

If a User with lower rights accessed the cookie of a Manager, it was possible to update the Operator Details. A privilege check has been added when saving the operator record to resolve this issue.

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-117513 · Issue 169033

History Audit information corrected for validation failures

Resolved in Pega Version 7.1.7

Following a validation failure in a flow action where validation is done in the post-processing activity, one line of history was being written for each validation failure in addition to one for the successful Submit. This was caused by the activity writing the history for a local flow action prior to calling the RunFlowActionActivity in which the validation occurs. This has been corrected to avoid history entry for error cases.

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