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-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-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-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.

SR-117583 · Issue 170260

Draft Mode now includes referenced rules for shape sub-processes

Resolved in Pega Version 7.1.7

If a a flow was created in Draft Mode and shapes were added, adding subprocess shapes and implementing one of the subprocesses created a list of Referenced Rules that did not include the sub-flow rules. This was caused by dangling connectors, and has been corrected by a call that will generate the Java for the flow even when this condition is present.

SR-117591 · Issue 171917

Improved Bulk Action checkbox handling

Resolved in Pega Version 7.1.7

In Case Manager Portal, when multiple work items (>3) were selected and transferred with Bulk Action, some were deselected and are not processed. This was traced to the select of checkbox calling an activity, followed by parent section refresh with refreshed all checkboxes. If checkboxes were selected while the refresh was in progress, the value for the next selection was not posted even though it appeared to be checked. This has been corrected to ensure all selected checkboxes are posted properly.

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