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-C28389 · Issue 374701

Added check for parent page when using 'save-as' in PM BundleTemplate

Resolved in Pega Version 8.1

Pega Marketing has a longstanding shipped section called BundleTemplate which is used to render a page-list of bundle members for emails. Doing a save-as of this section (without ANY changes) was resulting in runtime errors with the exception ":com.pega.pegarules.pub.clipboard.InvalidReferenceException: The reference .BundleOfferMembers(1).BundleOfferMembers is not valid. Reason: Entry handle must have a page name specified." This happened because the Section in grid was run on a page without a name, and the exception came from test id generation code which expected a complete path of the grid page list property. In this case the path is not complete as it starts with "." (dot) and there is not a top level named page. To resolve this, the code has been modified to not generate a test ID when the parent page does not exist in Clipboard.

SR-C28508 · Issue 368620

German language pack updates

Resolved in Pega Version 8.1

The German Language Pack (_de) has been updated to properly display the German text for rich text editors text like (Bold, Italic,) and the 'Check Spelling' tooltip.

SR-C28579 · Issue 384591

Delegated data types show correct tab header name

Resolved in Pega Version 8.1

When the delegated rules were opened from the case manager portal via configuration page in a multi DC portal, the tab name was shown as insname of the data type class. This was caused by the "pyInsHandle" property being configured for the name parameter for the landing page action. To correct this, the system will use "pyOriginatingLabel" instead of "pyInsHandle" in the pzDelegatedRulesGrid section to display the rule label.

SR-C28586 · Issue 377237

Error with fetching prompt value fixed

Resolved in Pega Version 8.1

When property was configured with declare expression and its read only value was given as 'Display text of selected options', it showed the standard value instead of the prompt value. This has been corrected with code changes to get the prompt value of the given configuration.

SR-C28586 · Issue 373798

Error with fetching prompt value fixed

Resolved in Pega Version 8.1

When property was configured with declare expression and its read only value was given as 'Display text of selected options', it showed the standard value instead of the prompt value. This has been corrected with code changes to get the prompt value of the given configuration.

SR-C28597 · Issue 369290

Logoff fixed for No SLO URL Authservice

Resolved in Pega Version 8.1

Recent changes made to Code-Security.Logoff to handle NO SLO URL defined in AuthService resulted in logoff not occurring properly. This has been fixed.

SR-C28672 · Issue 371101

Timing issue fixed with switchLocale refresh

Resolved in Pega Version 8.1

When using a function call to have a section refreshed so that it shows in Spanish, the section instead loaded in English and did not change. This was traced to a timing issue: the pega.clientTools.switchLocale method is asynchronous, and immediately refreshing Sections and Harnesses after the asynchronous call may not have time to reflect the changes. To resolve this, a callback mechanism has been introduced in the pega.clientTools.switchLocale method.

SR-C28691 · Issue 371875

Waterfall segment issues fixed

Resolved in Pega Version 8.1

After upgrade, issues were seen with waterfall segments with more than 10 groups in a set: 1) While deleting a criteria in a group, the control went to the top and did not come back. This has been fixed by adding code to get the name attribute using getAttribute().2) While moving groups up and down, the control went to the top and it was necessary to scroll down to find the rule. This was due to Menu options containing the refresh parent section request which was losing the focus. Code has been added to set the focus on the control from the point where the menu is getting launched.

SR-C28691 · Issue 371980

Waterfall segment issues fixed

Resolved in Pega Version 8.1

After upgrade, issues were seen with waterfall segments with more than 10 groups in a set: 1) While deleting a criteria in a group, the control went to the top and did not come back. This has been fixed by adding code to get the name attribute using getAttribute().2) While moving groups up and down, the control went to the top and it was necessary to scroll down to find the rule. This was due to Menu options containing the refresh parent section request which was losing the focus. Code has been added to set the focus on the control from the point where the menu is getting launched.

SR-C28801 · Issue 374737

Decimal validations fixed for offline mobile case

Resolved in Pega Version 8.1

On a mobile device using offline case it was possible to use multiple entries of grouping_separator without generating an error, but the Presentation configuration of Text Input control did not allow more than one separator in Google Chrome and Microsoft Internet Explorer . Example:"11,22" - worked "11,22.11" - generated error "11.22.22" - generated error "11,22,22" - generated error As a result it was possible to enter values as "12,3,3,3,3,3,3,3." or "12.3.3.3.3.3,4" and submit without any error and the Client Cache would be populated with the expected value "11111.76,null,null,null,null,null,777" , but after sync the clipboard contained "11111.76,null,,null,,null,777" This was due to the present client side validations not supporting validations based on locales, and a new regex expression has been added to pzpega_validators to fix invalid decimal number patterns like 45,,,,5434 , 45....5423 , 43.3,2354 , 54,.42324, etc.

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