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-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.

SR-A93038 · Issue 264675

Service REST requestor memory leak resolved

Resolved in Pega Version 7.2.2

The Asynchronous mode of executing Service REST acquired requestors from the pool while executing the queued jobs but did not return the requestors to the pool properly, causing a memory leak due to the requestors persisting in the system and not closing down. This has been fixed.

INC-157217 · Issue 631970

Field Service mobile refresh timing updated

Resolved in Pega Version 8.5.4

A configuration in the Field Service mobile app used to select and map data from a modal section to a wrapper section used "pega.fsm.mobileutil.reloadSection" to refresh the wrapper section and make the data visible after the mapping. If the refresh was performed after the initial login, the refresh was done on only a portion of the screen and resulted in incorrect data being shown to the user. However, continuing to fill in the section and then saving and reopening the task displayed the correct results. The issue was reproducible only on the first attempt after clearing cache/date: subsequent uses refreshed properly. This was traced to the timing of the configured actions, which caused the refreshSection action to be triggered before the runDataTransform action execution was completed. This has been resolved by adding code that will pause the action queue until the runDataTransform action completed.

SR-A20694 · Issue 255166

Added overlay modal dialog check in service intent

Resolved in Pega Version 7.2.2

The enter key press was not working as expected when initiating a search for a new service intent. While another service intent was currently open, 'enter' jumped back to the open service intent. This has been corrected by adding a target check for an overlay modal dialog.

SR-A20694 · Issue 256036

Added overlay modal dialog check in service intent

Resolved in Pega Version 7.2.2

The enter key press was not working as expected when searching for a new service intent. While another service intent was currently open, 'enter' jumped back to the open service intent. This has been corrected by adding a target check for an overlay modal dialog.

INC-157196 · Issue 629298

Deprecated service package features now require authentication

Resolved in Pega Version 8.5.3

Authentication has been added to deprecated features of the standard service package to improve security. If issues are encountered during product migration, please use the Deployment Manager.

INC-162198 · Issue 628704

Tracelist cleared to address parser exception in REST Service

Resolved in Pega Version 8.5.4

In a requestor pool of mixed types, HTTP and REST, the alert data was not initialized properly if there was a parse exception due to invalid data in the incoming payload. For example, last_input, first_activity, and last_step could all be left over from the prior HTTP service request. This was caused by the system pulling in seemingly unrelated activities for the "Last activity called" in the stack trace of a service when a single alert was created by two different service types which were sharing the same package, and has been resolved by explicitly clearing the tracelist for the service to prevent inaccurate information being reported in the logs.

INC-163043 · Issue 645391

PEGA SOAP Service MTOM attachment handling updated

Resolved in Pega Version 8.5.4

After configuring a PEGA SOAP service with the Enable MTOM checked, sending a SOAP request with attachment to the service returned an invalid request error stating "Value of content length header is greater than zero - [762], but this request has empty POST". Investigation showed that when the input request reached the getPostBytes method and inputstream tried to read it, there were no available bytes and end of file was detected. This was due to the inputstream having already been read in getMultiPartSOAPHandler() method in FileUploadHandler class. To resolve this, the system will update an 'if' condition in getPostBytes method to skip reading the request attachment when contentType is "multipart/related".

SR-A90314 · Issue 258672

DSM service will not start in non-web environment

Resolved in Pega Version 7.2.2

The import of NBAA using prpcUtils did not terminate due to the DSM services threads not being properly shut down during program termination. As DSM service is not needed in this circumstance, DSM service has been fixed to not start in non-web environments such as prpcUtils or prgit.

INC-150610 · Issue 627428

Argument number exception handled for SERVICES-PAL log configuration

Resolved in Pega Version 8.5.3

An issue with being unable to configure the SERVICES-PAL log file has been resolved by adding handling for an unlogged "wrong number of arguments" exception.

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