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.

INC-134171 · Issue 576432

Enhancements added to S3 repository implementation

Resolved in Pega Version 8.4.2

The following changes have been made to avoid redundant/unnecessary S3 SDK calls to look-up metadata for files/folders related to integrated S3 Repository API implementation:1) Provided storage/AWSSDK/enableSDKMetrics DASS to enable AWS SDK metrics for S3 repositories system-wide to troubleshoot performance issues 2) Added timers for Pega platform repository APIs. To see these timers in Pega application log, set log level to WARN for the log category pxIntegration.Repository.S3 and set log level to DEBUG for the logger com.amazonaws.latency 3) Optimized FileS3Adapter.getMetadata() by avoiding object-metadata lookup for directories and caching rootpath directory metadata for 5 mins 4) Handled exceptions while uploading file to S3 bucket and convey appropriate error message to RepositoryManager.createFile() API consumer 5) Refined DEBUG logging and introduced new loggers to emit stacktraces 6) Enhanced RepositoryManager.initCache() and FileStorageManager.registerStorageClasses() to maintain non-overridable repositories (that are initialized based on DASS/DNode settings on node start-up) and to prohibit overriding the same.

INC-96275 · Issue 553404

Attachment Migration tool updated for improved node crash handling

Resolved in Pega Version 8.4.2

During attachment migration from PegaDB to the S3 repository, a stream node crashed and left queue items in the queue. When the node restarted, these items were migrated successfully to S3. However, a manual restart of the attachment migration tool then ended up duplicating the items already successfully migrated. As part of handling the duplicate attachments, files with 0 bytes were created in S3 and the zero byte link was updated to the Data-WorkAttach-File instance. In order to handle this scenario, an enhancement has been added that will skip migrating attachments already migrated to repository or those having an empty attachment name.

SR-D36826 · Issue 550272

LastAccessTime returned for MDB listener

Resolved in Pega Version 8.4.2

The lastAccess time for the JMS listener was not being updated. Investigation showed that lastAccessTime was correctly updated whenever isStopping() was called, but isStopping() was not called for MDB listeners because the MDB listeners' state is managed by the app server. This caused accessTime to be empty. To resolve this, ListenerStateImpl has been modified to return mRequestTime as the lastAccessTime if the listener is of type MDB.

SR-D64558 · Issue 527678

AttachmentContent supports S3 storage

Resolved in Pega Version 8.4.2

Using a D_AttachmentContent data page to display the contents of an attachment by way of the pyGetAttachmentContent activity worked when using the Pega database for storage, but generated an error stating CMIS access was disabled after switching to S3 storage. This was traced to restrictions on Link-Attachment pages in Step 2, Line 64 of pyGetAttachmentContent to enable attachment stream retrieval from web storage and repositories by D_AttachmentContent, which has now been removed. In addition, pyGetAttachmentContent has been updated to behave the same whether a Link-Attachment page or Data-WorkAttach page is provided when populateAttachStream is set to false, and the rule documentation (description/usage) has been updated accordingly.

SR-D67142 · Issue 548643

Enhanced CMIS connector logging

Resolved in Pega Version 8.4.2

Additional diagnostic logging has been added to enhance investigating CMIS connector health.

SR-D67308 · Issue 552345

fetchWSDLDocument rule withdrawn

Resolved in Pega Version 8.4.2

The fetchWSDLDocument rule has been marked as withdrawn.

SR-D74376 · Issue 552261

Check added for string vs boolean for pzscan JSON

Resolved in Pega Version 8.4.2

When calling the CloudRemoteMaintenance/Work-/pzscan API, the response JSON had boolean values in the form of String which caused the JSON parsing to fail. The system was using ClipboardProperty.toStringValue() while generating outbound JSON from the clipboard page, which did not correctly interpret a boolean value. To resolve this, a check has been added that will assess the value and invoke ClipboardPage.toBoolean() when needed so that the value is converted as per type before generating the JSON.

SR-D83329 · Issue 546660

AWS S3 client SDK upgraded

Resolved in Pega Version 8.4.2

The com.amazonaws group has been updated to version 1.11.740 .

SR-D85940 · Issue 548334

AWS S3 client SDK upgraded

Resolved in Pega Version 8.4.2

The com.amazonaws group has been updated to version 1.11.740 .

SR-D87671 · Issue 551411

PegaCESvcsIntegrator security updated

Resolved in Pega Version 8.4.2

Security updates have been made which now require authentication to consume the services from the PegaCESvcsIntegrator package.

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