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-C90261 · Issue 428124

Hotfix installer updated to adhere to installorder file included in the package

Resolved in Pega Version 8.1.4

In order to ensure hotfixes are always installed in the proper order, the installer has been updated to iterate over a set that is ordered according to the INSTALLORDER.PEGA file included in the DL file at packaging time.

SR-C90467 · Issue 429609

Validations are correctly run on rescheduled reports

Resolved in Pega Version 8.1.4

When using the OOTB schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.

SR-C91121 · Issue 430390

Data Page seatch results have expanded data available to view

Resolved in Pega Version 8.1.4

It was not possible to expand a search result and see Ruleset, Updated by, etc, for Data Pages. This was traced to the Layout Properties of section pzSearchDrilldown having a visibility condition of .pzCategoryActionKeys != 'Rule-Declare-Pages' after being reconfigured during prediction studio implementation for rule transition. To resolve this, the necessary related table for data pages has been added to the pzSearchDrilldown section.

SR-C91156 · Issue 429630

Autocomplete Menu Selection for privileges tab Role updated

Resolved in Pega Version 8.1.4

When a few characters were typed in the autocomplete for "Role" in the privileges tab and the desired value was selected, the selection did not stick. The second time the value was selected it was retained. Investigation showed that the post value source element had a stale reference after section reload, and this has been resolved by adding code to re-initialise the reference with the latest element.

SR-C91370 · Issue 429580

System updated to jackson-databind-2.9.8.jar

Resolved in Pega Version 8.1.4

The jackson-databind jar has been upgraded to v2.9.8.

SR-C91501 · Issue 428973

Support added for base64Binary type in the SOAP envelope

Resolved in Pega Version 8.1.4

In order to support the sending of files more than 10 MB in size as a SOAP attachment, a condition has been added to populate base64Binary type as a multipart message in the SOAP envelope. This allows a text node with binary content to be optimized for xop/MTOM.

SR-C91521 · Issue 428629

DX API updated for improved security

Resolved in Pega Version 8.1.4

Modifications have been made to the DX API to improve system security.

SR-C91750 · Issue 429617

Summarized report after editing shows Count as expected

Resolved in Pega Version 8.1.4

When creating a report with a number of fields and summarizing it in the report browser, the summary gave proper counts. However, after clicking on "edit report" and then running summarize on the same column, the generated report gave the Sum of the number column instead of the Count. To resolve this, the implementation used to update a hidden value for the dropdown has been set to initialize to the Count option.

SR-C91907 · Issue 433772

Thread context preserved when processing a case in interaction

Resolved in Pega Version 8.1.4

Thread context was not being preserved correctly when a case was opened from an interaction. This has been corrected.

SR-C91927 · Issue 431510

ValidateSurveyStream updated to ensure validation runs on a named page

Resolved in Pega Version 8.1.4

After creating new survey rules, trying to re-validate and save in survey-specific rules was failing to re-validate in standard/personal edition. This was an issue with the ValidateSurveyStream activity running on an unnamed page: in this activity, the stepPage name is set to a parameter and passed to datatransform for the processing of the rule. Since the steppage was unnamed, an exception was thrown. To resolve this, steps have been added in the ValidateSurveyStream activities for question, question group, and survey that will copy the primary page into the named page and pass it as a parameter.

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