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.

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-153805 · Issue 627966

Mobile app language remains consistent after data sync

Resolved in Pega Version 8.4.5

When using a Field Service Mobile App where the locale of all workers was set to nl_NL, the UI was intermittently flipping from NL to EN and and back again. This was traced to the locale of the requestor (field worker) being lost during synchronization of the mobile app data to the server, causing the UI to fall back to the default value of EN. This has been resolved by ensuring the requestor always uses the chosen locale for the operator.

INC-155640 · Issue 622977

Mobile logging updated for data page required parameters

Resolved in Pega Version 8.4.5

After upgrade, the number of warnings increased substantially in the mobile app log file for D_Pages, specifying "Required parameter X for data page X cannot be blank." This was traced to the forced logging related to missing required parameters for Parameterized DataPages during DeltaSyncs. In order to increase the value of the logging, the process has been moved from being called before packaging the Data Page to being printed later in packaging code and set to warn only about any unsupported data page configuration with required parameters.

INC-155752 · Issue 622770

Hidden Question pages and answers will be saved to DB

Resolved in Pega Version 8.4.5

After a question page was shown and some values were entered, going back to the question and reverting an option caused the question page to not be visible, but the answer values persisted in the clipboard and were eventually saved into the database. This was a missed use case for Question page smart shapes, and has been resolved by updating the pzSetQuestionPageParams data transform so that whenever a question page is evaluated to either to show/hide, when the question page visibility is set to false and the pyClearAnswerValuesWhenQPHidden 'when' rule is overridden, the corresponding values will be wiped from the clipboard and only the required values will be saved to the database. However, please note this is not supported for branching logic and visibility conditions should be used instead.

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