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-117509 · Issue 168620

Tuned positioning of 'Party Role' by eliminating white space

Resolved in Pega Version 7.1.7

The displayed Party Role in Work Parties was poorly positioned due to unnecessary white space. This has been fixed.

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-117573 · Issue 171739

Fixed disappearing menu in modal dialog for IE11

Resolved in Pega Version 7.1.7

After launching a local action in a modal dialog from a Navigation rule while using IE11, dismissing the local action caused the navigation rule to disappear until the browser was manually refreshed. This was caused by a routing issue with the menubar call that failed to correctly reload the menu, and has been corrected.

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.

SR-117606 · Issue 173816

Fixed portals enhanced for IE10 and IE11

Resolved in Pega Version 7.1.7

An enhancement has been added to the system to ensure portals will render accurately in IE10 and IE11.

SR-117674 · Issue 170571

Smart Shapes use properly limited to work class

Resolved in Pega Version 7.1.7

An error in the code made Smart Shapes visible when creating a data-class flow. Attempting to include them by dragging them into the flow design pane resulted in an "empty" utility shape that was missing many of the options normally offered. Because Smart Shapes are designed only for work classes, Smart Shapes will not be visible in shape menu when a flow is created in data class.

SR-117744 · Issue 172508

BodyVisibleWhen updated for repeating tab layouts

Resolved in Pega Version 7.1.7

Previously, repeating tabbed layouts had the option of BodyVisibleWhen in the properties of the layout for referring to a 'when' condition of the pagelist property. After migration, attempting to use the 'when' condition took the class of the section and not the class of the pagelist. The ValidateSection and its includes have been modified to properly consider the tabbed/column repeat 'when' condition validation.

SR-117752 · Issue 171493

Changed decimal values to comma values for NL/SE localization

Resolved in Pega Version 7.1.7

The Dutch and Swedish convention for decimals is to use a comma as the separator instead of a dot. This use was not included in the localization so clicking on submit caused the comma values to be converted with a decimal point that multiplied the value by 100. (1200,00 is twelve hundred euros; the value became 120,000.00 - one hundred and twenty thousand euros) This has been fixed so the values are correctly handled with commas when localized to NL or SE.

SR-119243 · Issue 175219

Changed decimal values to comma values for NL/SE localization

Resolved in Pega Version 7.1.7

The Dutch and Swedish convention for decimals is to use a comma as the separator instead of a dot. This use was not included in the localization so clicking on submit caused the comma values to be converted with a decimal point that multiplied the value by 100. (1200,00 is twelve hundred euros; the value became 120,000.00 - one hundred and twenty thousand euros) This has been fixed so the values are correctly handled with commas when localized to NL or SE.

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