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-120326 · Issue 564437

Landing page refresh modified to avoid frequent reloads

Resolved in Pega Version 8.1.9

Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.

INC-130158 · Issue 572051

iOS file attachment works in Safari

Resolved in Pega Version 8.1.9

Attaching PDF and images from iOS devices using Safari was not working. This was traced to iOS 13 launching the file browser by default if the file-input element had an accept=/ attribute value pair, and has been resolved.

INC-136752 · Issue 587728

Adding handling for custom image on S3 storage space

Resolved in Pega Version 8.1.9

When using an S3 repository for Content storage, trying to create a new space with a custom image did not upload the image. Investigation showed that when attachment storage is configured as an external repository, the pyAttachStream property which is used to create the the thumbnail was getting cleaned as part of the saving logic. This has been resolved by adding an update that will hold the attachStream value in a local property before calling attachment save.

INC-141920 · Issue 595139

Unable to delete the Spaces after loggin off

Resolved in Pega Version 8.1.9

If a Space was created and then deleted in the same login session, the delete worked as expected. If the Space was created and then actions were taken to delete it on a subsequent login, the Space was not actually deleted. Investigation showed this was due to v8.1 not having a stream/blob (PZPVSTREAM) in the pc_work_group table, and this behavior was the result of extra properties included on the page. To resolve this, the extra properties on the page will be removed before the obj-save/commit .

SR-D85624 · Issue 552697

Corrected Microsoft Internet Explorer displaying checkboxes as sliders

Resolved in Pega Version 8.1.9

Checkboxes were displaying as sliders in Microsoft Internet Explorer version11.1304.17134.0 due to Microsoft Internet Explorer returning Table pc 2.0. Since Pega HTML class includes tablet, .tablet related styles were getting picked up and displaying the checkboxes in tablet mode. To resolve this, a check has been added to pyIsTablet to evaluate correctly at runtime.

SR-D91532 · Issue 556406

Resolved Clear Cache error for mobile client

Resolved in Pega Version 8.1.9

When attempting to clear local storage while logged into the Mobile Client, the error message "You need to be able to connect to the server in order to clear the storage" appeared. This was traced to the application being configured to disable a user's web session immediately after log in, and was due to the "Clear Cache" functionality failing while attempting an AJAX request to invoke the server's "pzAmIOnline" activity. While there was a workaround of using the check box "Access group requires a connection for portions of the application", this has been resolved by updating the Settings - Clear Cache functionality in order be able to detect if it's online in a different way.

SR-D95428 · Issue 555260

Security added to retrieving operator list by URL extension

Resolved in Pega Version 8.1.9

It was possible to append information to the application URL which allowed an unauthenticated user to find a list of operators. This has been corrected, and will now result in the message "There has been an issue; please consult your system administrator."

INC-122112 · Issue 599795

Updated SLA table clearance

Resolved in Pega Version 8.4.4

After cases were resolved, SLA entries were not getting cleared from the SLA table. This caused the SLA table to have a huge number of Overall SLA and PendFlow details present for cases that were resolved or moved to the next state, which impacted case processing via SLA Agent. This was traced to SLA queue-items not being removed by delete-deferred as expected, and has been resolved by invalidating the deferred operations and scheduling item removal.

INC-125200 · Issue 572134

Documentation updated for binary REST response

Resolved in Pega Version 8.4.4

The online help documentation has been updated to clarify the instructions for REST endpoints that return binary data. In some cases, the data is returned in a MIME multipart structure. It can also be returned as the response body. In the latter case, mapping the message body to a java object property will cause the binary data to be mapped as a java byte array value. Mapping the message body to a single value text property will cause the binary data to be mapped as a Base64 encoded text value.

INC-125633 · Issue 589575

Oracle performance improvement

Resolved in Pega Version 8.4.4

Poor performance was seen when importing a RAP with schemas using Oracle. To resolve this, an update has been made which will set the Oracle tuning parameter at the session level by altering the setting "_OPTIMIZER_PUSH_PRED_COST_BASED"=false before the SMA query involving all_constraints. The setting will be returned to true after the execution of the SMA query. This is controlled through the prconfig setting '"database/performance/smaqueryperformanceenabled" which defaults to true so the setting and unsetting of the Oracle parameter is automatic.

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