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.

SR-D24527 · Issue 504402

Improved requestor cleanup

Resolved in Pega Version 8.2.5

Batch- and Browser-type Requestors were building up over time in both the Admin Studio and in the PegaRULES log and not removed until the system was restarted. This has been resolved by adding two extra cleanupRequestor calls to the Email Listener implementation.

SR-D29034 · Issue 500681

Added support for JSON mapping of deep nested pagelist objects

Resolved in Pega Version 8.2.5

An exception occurred when using a JSON data transform in the service activity to map the clipboard data to JSON on the third level of a structure formed as Pagelist-->page-->pagelist. To resolve this, support has been added for nested pagelist mapping with deep nesting of objects (configured for one sided actions) and arrays.

SR-D33003 · Issue 511230

Queue Batch activity correctly passes chlld process access group

Resolved in Pega Version 8.2.5

When users attempted to create an index using the schema tools landing page, an error displayed in the table history stating "Create index failed". Investigation showed that this happened when a user was authenticated without the PegaRULES:DatabaseAdministrator role and then switched to an Access Group with the PegaRULES:DatabaseAdministrator role. The issue was traced to the activity that launched the batch requestor missing the parameter pzUseCurrentAccessGroupForChild due to the Queue Batch activity only passing the default access group authorization. This has been resolved by adding code to pass the additional authorization which will allow users to create an index in this scenario.

SR-D33214 · Issue 514023

Added safeURL encoding for Japanese characters in attached filenames

Resolved in Pega Version 8.2.5

It was not possible to preview a Japanese-titled PDF file attached on a work object. Investigation showed that in case of Japanese characters, file names were not being correctly encoded during the fetch request when JBoss was used. The retrieval worked correctly under Tomcat. In order to ensure consistent encoding, the safeURL API will be used for constructing the URL and for the activities DisplayAttachFile and pzDownloadFromRepository which add the ContentDisposition header.

SR-D33227 · Issue 510825

Check added for lock expiration when using Save for Default locking

Resolved in Pega Version 8.2.5

With the default case locking policy, during the process from creating a Case Object to Submit it was possible for multiple users to edit and save the same work object if the lock expired for the original user. No warnings appeared. To resolve this, handling has been added for a lock expiration scenario: previously, Save for Default locking was not considered. This has now been updated with a check that will evaluate whether or not the lock is gone before attempting to save.

SR-D37779 · Issue 514411

Dynamic System Setting added to Invalidation query to tune performance

Resolved in Pega Version 8.2.5

Running a RuleInvalidation query on an SQLServer database with a large amount of data was causing performance issues. To improve performance, a force order hint has been added which can be enabled with the Dynamic System Setting racache/useForceOrderHintForInvalidationQuery.

SR-D40785 · Issue 515099

WorkPageName preserved during passivation so attachments are correctly tracked

Resolved in Pega Version 8.2.5

When a work object was left open but inactive for a period, using the delete button in the pyAttachFieldRequired section caused the deletion of the Attachment Links for the 500 most recent attachments in the system with the same value for the AttachmentFieldName, regardless of which work object they were attached to. This was due to the delete attachments activity being executed with missing parameters: since data page loading was disabled and read-only data pages are not passivated, the value for the autopopulate property 'WorkPageName' was passed as empty. To resolve this, the data page will be preserved or reloaded as appropriate so the WorkPageName is maintained.

SR-D40883 · Issue 511123

Updated SendEmail shape to remove newline code from the subject line

Resolved in Pega Version 8.2.5

When using the SendEmail shape to send outgoing email, the message contained HTML tags on the subject line that caused it to be split and copied into the email body. This has been resolved by updating PegaEmailClientImpl.prepareMessage() to replace new line characters with spaces in the subject.

SR-D41228 · Issue 512107

DSS added to Request Only Connect SOAP for Robust

Resolved in Pega Version 8.2.5

After upgrade, creating a new SOAP integration set to "Request only" in the Service tab and then running the activity showed requests coming with no response, then failure after three tries. This was traced to previous changes made to support Robust behavior and log failed asynchronous calls, and has been resolved by modifying the Robust support and moving it to a DSS. If “EnableRequestOnlyFaultMapping” is set to “true”, then the ANON_ROBUST_OUT_ONLY_OP option will be used, otherwise, the default behavior will be ANON_OUT_ONLY_OP.

SR-D42406 · Issue 510669

Support added for UTF-8 charset in Connect-REST pyRequestAttachmentPage

Resolved in Pega Version 8.2.5

When using Connect-REST with pyRequestAttachmentPage, Polish characters like "ó" or "ł" were converted to "?". This did not happen when pyRequestAttachmentPage was not used. This was due to the post request body using a multipart handler that ignored the charset being passed in and considered it a respective enum type for Application/json internally instead. This has been resolved by adding support for charset UTF-8.

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