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-A89637 · Issue 259256

Search for Work gadget updated to accept "StartsWith"

Resolved in Pega Version 7.2.2

When using a fixed portal, the Search for Work gadget was not working for the option "Starts With" when pxOperatorMap rule was being called from newly added Property-Map-Value methods. This was caused by pxOperatorMap not having a return value for StartsWith, causing the default value"=" to be returned. This has been fixed by adding a return value for "StartsWith", "NotStartsWith", "EndsWith", "NotEndsWith", "Contains", "NotContain", "IsNull", and "IsNotNull" in pxOperatorMap.

SR-A90472 · Issue 258243

Population handling added for null value flowType property

Resolved in Pega Version 7.2.2

While launching the case local action, a clipboard error was generated indicating the InternalStageFlow failed to find the named RULE-OBJ-FLOW. This was caused by a null flowType property value in the PegaProComUtilities populateFlowActions--(ClipboardPage, ClipboardPage, PublicAPI) function due to the order of actions, and the system has been updated to seek the flowType property of an assignment if it encounters a null value.

SR-A91743 · Issue 259136

Security update for pxInitials control

Resolved in Pega Version 7.2.2

XSS (Cross Scripting Filter) has been added for potentially exploitable parameters in the pxInitials control.

SR-A75998 · Issue 253191

Improved SOAP envelope cache for WSA/WSSE use

Resolved in Pega Version 7.2.2

After configuring and successfully using Connect-SOAP to a non-secure Endpoint, enabling WSA and WSSE for the connect-SOAP configuration and then disabling it again generated the error "Caused by: com.pega.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present". This was due to the way the SOAP envelope was being cached and the code has been updated to correctly reflect the desired header processing.

SR-A69786 · Issue 251702

EmailService CC parameter correctly mapped

Resolved in Pega Version 7.2.2

After upgrade, the inbound email processing was not capturing the Email Service request parameter "CC " in the service page. This was due to an unwanted space in the CC field name mapping which has now been removed.

SR-A20058 · Issue 250683

PEGA0020 alert updated for full interaction time

Resolved in Pega Version 7.2.2

An error with PAL timer statements caused an Null Pointer Error during connect SOAP execution due to socket read time not being accounted for in the PEGA0020 alert. This has been fixed.

SR-A22183 · Issue 249190

Fixed default node values error in XML

Resolved in Pega Version 7.2.2

An issue was found where a default value set for node elements was not overriding the optional checkbox and blank tags were being created in the XML page. This has been fixed.

SR-A64734 · Issue 251922

OpenSAML decoder updated to allow Okta implementation

Resolved in Pega Version 7.2.2

Attempting to configure Okta was generating exceptions due to decoding issues with the XML. In order to better support this third-party program, flexibility has been added to handle IPD responses received without the expected URL encoding.

SR-A64734 · Issue 252332

OpenSAML decoder updated to allow Okta implementation

Resolved in Pega Version 7.2.2

Attempting to configure Okta was generating exceptions due to decoding issues with the XML. In order to better support this third-party program, flexibility has been added to handle IPD responses that are received without the expected URL encoding.

SR-A76475 · Issue 255252

SOAP Service generates nillable attribute in WSDL

Resolved in Pega Version 7.2.2

Attempting to generate WSDL with the Nillable attribute was not working as expected. This was due to an error in referring to the property name to fetch the nillable checkbox value in XMLTreeViewUtils.java and has been fixed.

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