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-A18193 · Issue 238469

SystemCleaner correctly purges pr_perf_stats

Resolved in Pega Version 7.2.1

It was noticed that SystemCleaner was working well except for a periodic dramatic purge that suddenly filled logs and sometimes caused a system crash. When BIX runs via command line, this updates the associated DSS in the application. If the DSS usage/usagetrackingenabled or its associated prconfig.xml setting are set to false, Step 12 of the SystemCleaner does not perform a number of activities including regular purging the pr_perf_stats table. This has been modified to remove the setting usage/usagetrackingenabled from prconfig.xml as agents are by default enabled.

SR-A18404 · Issue 235467

New parameter to disable logging of Tidy PDF processing warnings

Resolved in Pega Version 7.2.1

When purge/archive was enabled, the system logs were filling with Tidy warning errors during PDF conversion. To resolve this, the new parameter 'pyShowWarning' has been added to the HTMLTOPDF Activity: set it to 'false' to avoid Tidy processing warnings in logs.

SR-A18624 · Issue 239177

Fixed post-upgrade data table conversion to local storage

Resolved in Pega Version 7.2.1

After upgrade, updating a data table into a local storage source generated the error "Cannot change keys for a class with (725) instance(s) ". This occurred when the local variable ?classKeysChanged? is true, which happened during comparison of the Key fields of the step page (classPage) and the primary page (ClassForm) because the order of the keys had changed even though the number of keys were same. The "AddProperties" activity has now been modified to check if there are keys already set in the class and if there are any, then skip resaving the class and exit the activity.

SR-A18694 · Issue 246976

Method changed for locating Word Templates folder

Resolved in Pega Version 7.2.1

The method used to obtain the Word templates folder always lower cases the folder path, but this poses a problem for the Turkish locale when the path contains capital I with no dot. Turkish has two variants of I - one with dot and one without dot. To resolve this, the Office templates folder path will be determined based on a combination of certain registry keys dependent on the Word version.

SR-A18813 · Issue 236196

Support added for auto-generated numeric IDENTITY columns in RD

Resolved in Pega Version 7.2.1

Because IDENTITY auto-generated columns were not supported , RD did not identity the column of type numeric() IDENTITY and generated an error when accessing a table with NUMERIC column types in SQL Server 2012. Numeric() TYPE was already supported for generation in RD, and an SQL connector has been added to handle tables with numeric() IDENTITY as well.

SR-A18952 · Issue 236936

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-A19075 · Issue 236452

Corrected class structure created by SOAP Integration Wizard

Resolved in Pega Version 7.2.1

An issue was found in the class structure created by the SOAP Integration wizard after upgrade. This has been fixed by updating the pyCreateGenerationRequest data transform to append servicename.

SR-A19167 · Issue 242469

Modified decision table handling for Connect-REST

Resolved in Pega Version 7.2.1

Authorization problems in opening the pyOutboundIdentifierDecoder decision table were causing Connect-REST failures. While it is recommended to only initialize the decision tables for legacy mapping DSS(json/legacyMapping) and not initialize the decision tables for normal JSON mapping, ServiceHelper and RulegeneratorREST have been updated with a check to properly handle the presence of decision tables.

SR-A19172 · Issue 236714

Managed unique constraint violation error for BIX

Resolved in Pega Version 7.2.1

When running multiple extracts using agents and pxExtractDataWithArgs at the same time, a unique constraint violation error was produced in the logs. This occurred when the extracts had the same time stamp down to the millisecond and an entry is added to the pr_log table when each extract starts. The pzInsKey for two extracts that run at the same time was identical, thus leading to this error. To resolve this, the thread name will be appended when the extract is run from an activity.

SR-A19281 · Issue 235998

Dialogue handling updated for WS-Security Profile password

Resolved in Pega Version 7.2.1

The presentation format for the password field of the WS-Security Profile outflow page has been changed to no longer display the password in the clear in any resulting dialogue.

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