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-A20982 · Issue 243968

Repeat grid clipboard index fixed

Resolved in Pega Version 7.2.1

On deleting a row from the repeat grid and proceeding, the deleted row was reappearing due to the improper resetting of a clipboard index when a grid has multiple references. The indexing has been fixed.

SR-A21015 · Issue 239858

AddTime calendar logic updated

Resolved in Pega Version 7.2.1

An issue was found with the final output of using the AddTime function in a Business Calendar with Australian Time Zone to add the difference between GMT and Australian time. In the internal APIs being used by this function, whenever parameters to addTime() were given in such a way that the time to be subtracted was same as the difference between the time of a given input date, start time of a business day, it was considered that there was nothing to add to input time and hence incorrect result. The logic in the engine API, CalendarUtitlity.addTime() which is used in addTime() function, has been changed to correctly calculate the desired time.

SR-A21017 · Issue 239317

Parameter label mismatch corrected for import

Resolved in Pega Version 7.2.1

During upgrade, activities or functions which had Parameter type 'Double' were automatically converted to String data type upon Import into the target Environment even when the XML indicated DOUBLE. This was an issue with rendering the value in the UI: the pyLabel for double parameter type was "Double" not "DOUBLE" in the Data Transform rule pyLoadDataTypes, which didn't match. The activity has now been updated to use DOUBLE.

SR-A21081 · Issue 230410

Strategy rule information added to tracer

Resolved in Pega Version 7.2.1

A tracer invoked with SOAP service --> Activity --> Flow --> Interaction rule --> Strategy was only showing the the executed components in its (reversed) execution order and did not show the execution strategy path. This has been fixed.

SR-A21098 · Issue 246780

Updated row delete authorization failure error message

Resolved in Pega Version 7.2.1

The delete button at the top of the ListViewEditor was correctly configured to delete or not based on permissions, but the proper error message did not appear when the edit attempt failed. The function will now show the message "You are not authorized to delete row." in cases where there was no permission to delete the instance.

SR-A21573 · Issue 241299

Security update for Web Service Policy RampartConfig signaturePassword

Resolved in Pega Version 7.2.1

Appropriate changes have been made to support password obfuscation in signaturePassword and userPassword elements of RampartConfig elements configured in Ws-Policy rule form.

SR-A21588 · Issue 241928

Name retrieval updated for node sub-units

Resolved in Pega Version 7.2.1

A retrieval error for the sub-unit name of a node was causing a "Cannot render section" error in the Organization Chart tab. This has been corrected.

SR-A21597 · Issue 241378

Request Only' I/O timeouts updated for Connect HTTP

Resolved in Pega Version 7.2.1

The Request Only checkbox option on Connect HTTP rules is intended to optimize IO latency for fire-and-forget use cases. The code that implements the connector was performing a full request/response HTTP call, even when the Request Only option had been selected. This sometimes caused long IO delays in the connectors. This update leverages the ability of the HTTP client to set a socket read timeout value on the response coming back from the server, which has now been set to 1 millisecond (zero milliseconds is not an option) in the cases when the Request Only feature has been enabled on the connector rule. The HTTP socket connection will time out immediately after the request message has been sent and eliminate any overhead of consuming the HTTP response data. Any connection failures will still be reported as exceptions.

SR-A21792 · Issue 242548

Saver.addBatch updated to log exception details

Resolved in Pega Version 7.2.1

To improve diagnostics, an SQL exception in the Saver class will log the actual exception instead of a null pointer.

SR-A21810 · Issue 231480

PreClose updated to better handle inactive DC documents

Resolved in Pega Version 7.2.1

The PreClose extension point was not always being triggered for inactive DC documents utilizing the pzClearRecentItem and pzClearAllRecentItems APIs due to stale settings. The correct this, the handlegadgetLoad method has been updated to delete the docObj after the document has loaded.

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