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-A5746 · Issue 213321

Ensured DateTime maintains read-only state when used with editable dates

Resolved in Pega Version 7.2

In a DateTime control with a read-only format set differently from an editable date format, the read-only format was being set to an editable date format when other fields were refreshed. This was an issue with calling the API, and has been corrected.

SR-A6169 · Issue 204154

Corrected compilation error when using param.value in Repeat Layout label

Resolved in Pega Version 7.2

A compilation issue was encountered when a parameter was used in a repeat section cell due to the paramStrValue being double encoded. This has been resolved by adding a check that will skip the extraneous encoding.

SR-A10406 · Issue 223580

Check added for page context when dropdown used in nested repeating grids

Resolved in Pega Version 7.2

A Dropdown placed in nested repeating grids with the event request onclick action "Post value" disappeared from the DOM on select of an option. This was due to an incorrect page parameter, and a check has been added to send the correct contextPage.

SR-A2779 · Issue 213357

XMLSecurity library updated to ensure proper SAML STS token signature verification

Resolved in Pega Version 7.2

Classes of Repackaged version of XML Security library were conflicting with JDK/container and causing sporadic signature failures. The ApacheXMLDSig which gets registered as part of the initialization of WSS4j often conflicts with the providers with same name but loaded earlier during server startup. This has been resolved by modifying the XMLSecurity library to register the provider with a different/unique name that will not conflict with any of the standard registered providers.

SR-A4515 · Issue 210886

Updated Outlook functions used by SendEmailMessage

Resolved in Pega Version 7.2

The SendEmailMessage function is used in conjunction with email clients to send a meeting invite from the PRPC application and have the accepted invitation and subsequent reminders appear on the recipient's calendar. This relies on key value pairs to define different functionalities at the client's end when the file is received. Integration with Outlook is a legacy feature of this function, but does receive some maintenance to maintain viability. To that end, the system has been updated to resolve issues with the calendar interface to Outlook concerning the trigger of meeting invite reminders at the client's end and to better handle the time zone conversion of that meeting. In addition, updates have been added to show the name of the meeting organizer instead of the email id, and the text used by the MeetingData.pyDescription function to set the meeting invite description will also be seen in the mail body.

SR-A3548 · Issue 210897

Updated Outlook functions used by SendEmailMessage

Resolved in Pega Version 7.2

The SendEmailMessage function is used in conjunction with email clients to send a meeting invite from the PRPC application and have the accepted invitation and subsequent reminders appear on the recipient's calendar. This relies on key value pairs to define different functionalities at the client's end when the file is received. Integration with Outlook is a legacy feature of this function, but does receive some maintenance to maintain viability. To that end, the system has been updated to resolve issues with the calendar interface to Outlook concerning the trigger of meeting invite reminders at the client's end and to better handle the time zone conversion of that meeting. In addition, updates have been added to show the name of the meeting organizer instead of the email id, and the text used by the MeetingData.pyDescription function to set the meeting invite description will also be seen in the mail body.

SR-A7105 · Issue 215067

Corrected When Display format handling for DateTimeControl

Resolved in Pega Version 7.2

If the read-only formatting value was checked in the pxDateTime control for the When Display value, selecting the same value twice from the calendar caused the formatted value to be lost. To correct this, the populateSubmitableField API in pzpega_ui_calendar_dbp js file has been updated to set the data-display-value attribute before setting the value and enabling the data-formatting attribute.

SR-A7485 · Issue 216800

Visible When Conditions working for buttons in Harness

Resolved in Pega Version 7.2

Due to changes in the condition expression formatting, Visible When Conditions were not working as expected for buttons in the harness after upgrade. A check has been added to evaluate the structure and apply the correct visibility expression.

SR-128961 · Issue 208349

Added check for naming conflicts when upgrading Oracle

Resolved in Pega Version 7.2

When attempting to upgrade a single schema on Oracle database, running the generateddl script failed with a NullPointerException. This was caused by database tables which had a column name called 'SYS_ID' as part of the primary key. Since Oracle uses system-generated names beginning with "SYS_" for implicitly generated schema objects and subobjects, Oracle discourages the use of this prefix in the names explicitly provided to the schema objects and subobjects in order to avoid possible conflicts in name resolution. To resolve this, a tester has been added to the system to check for this naming use and issue a warning.

SR-130442 · Issue 212468

Added support for localization of the 'Advanced' value of the When rule

Resolved in Pega Version 7.2

If the "Advanced" value was localized in the When rule form, it failed as it was trying to compare with localized text. To resolve this, WhenTabListener has been modified to use the ID attribute instead of text for comparison.

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