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-A13931 · Issue 227032

validation errors shown with datetime control

Resolved in Pega Version 7.2.1

If a server error occurred, client validation errors were not shown when the next focusable element was in datetime control. The issue here was that the Control change event was not properly bound to the calendar control in case of immediate focus, and this has been corrected.

SR-A14004 · Issue 231765

Flow designer XML fixed when using copy/paste

Resolved in Pega Version 7.2.1

Copy and paste are available in the Flow Designer, but tickets where the End shape was copy/pasted and a new ticket set created for the new End shape resulted in incorrect XML. To correct this, the flowmethodbody function will use pyTicketShapes instead of pyModifierRefs for java generation.

SR-A14014 · Issue 227004

HTTP Connector API will dynamically set TLS protocol

Resolved in Pega Version 7.2.1

The HTTP Connector was failing to connect using TLS v1.2 protocol due to the SSL Protocol being hardcoded to TLS while setting SSLContext. To fix this, the system will not pass the protocol while instantiating SSLContext, but will leave it to the API to set to highest protocol from JRE.

SR-A14106 · Issue 227981

Improved sender handling for custom email activities

Resolved in Pega Version 7.2.1

A custom email related activity was producing an authentication exception due to an attempted call to a User ID stored in Param.FromUsername made after that parameter was cleared by SendEmailNotification. To avoid this, if Param.FromUsername is blank, it will be set to the value of Param.AccountID.

SR-A14108 · Issue 242466

Better handling for rules considered duplicates

Resolved in Pega Version 7.2.1

A legacy API was not properly resolving rules present in an earlier ruleset version, leading to the creation of additional rules. The system will now consider rules already present in the earlier ruleset version and present the Other duplicate screen asking to skip, overwrite, or rename the rule.

SR-A14132 · Issue 232550

Improved handling for values starting with "." in Developer Portal Explorer

Resolved in Pega Version 7.2.1

A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.

SR-A14132 · Issue 233457

Improved handling for values starting with "." in Developer Portal Explorer

Resolved in Pega Version 7.2.1

A value starting with "." was being treated as a property and causing an exception error when using the Recent Explorer in the Developer portal. A catch has been added to resolve this issue.

SR-A14151 · Issue 244440

Autocomplete select updates as expected

Resolved in Pega Version 7.2.1

An intermittent problem was found with autocomplete that selected a previously set value if text was typed in the autocomplete box and the value was selected instead of the search text. This was traced to a press of the capslock key being interpreted as an unprintable character, causing an abort of the request and change tracker not having the correct update. The function processkey of autocompleteag.js has now been updated to not abort the request when a non-printable character is typed.

SR-A14168 · Issue 230039

Unique page names generated for nested child work items

Resolved in Pega Version 7.2.1

When multiple child work items were created using pxAddChildWork in one transaction, the same page name was getting used and causing errors. This has been fixed by making pagename unique by appending currentdatetime.

SR-A14230 · Issue 230423

IconRequired fixed for repeating layouts

Resolved in Pega Version 7.2.1

The iconRequired span was only being generated for the first row of any repeating layout structure. This has been fixed in the GenerateCellContent RUF.

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