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-D54120 · Issue 541351

Improved handling for attachments not using UTF-8 encoding

Resolved in Pega Version 8.3.2

When an email was received that used a charset encoding other than UTF-8, special characters in the HTML body were not displayed and instead the replacement character was shown. To resolve this, the system will read the encoding from the email rather than use the meta tag, and will add the attachment's HTML encoding information in Data-WorkAttach-File so that the same can be used to process and display the original HTML properly.

INC-166048 · Issue 659534

Navigation icons added for use in offline mobile

Resolved in Pega Version 8.7

When using an offline mobile app, clicking on an image / link on the home page for navigation resulted in the error “Resource missing. See client logs.” This was traced to a missed use case that resulted in some icons not being available in the package, and has been corrected by including the following: webwb/py-menu-toggle.png webwb/pzgrid_downarrow.png webwb/pymenuleftarrow.png webwb/pymenurightarrow.png webwb/pymodal_mask_img.png webwb/py-grid-sort-down.svg

SR-D42451 · Issue 518066

ExecuteRDB call updated to use NativeSQL for blob

Resolved in Pega Version 8.3.2

After creating a test activity to clear data set records that used the DataSet-Execute method and passed the data set name and truncate operation, only 51 records were deleted in a single run when the data set had more than 51 records. Investigation showed that for blob tables, the database truncate operation was using executeRDB with an empty results page, i.e. it didn't specify pyMaxRecords, which on some databases might have limited the number affected records. To resolve this, the executeRDB call in the database truncate operation has been modified to use NativeSQL for blob tables.

INC-192159 · Issue 691022

Handling added for designtime page used in runtime

Resolved in Pega Version 8.7

After creating a survey with branch Create survey cases routed to different actors, some cases missed the assignments and were left idle with no access to progress. Survey cases (with branches) having the 'when' conditions in flow connectors experienced this intermittently in production. This was traced to the use of D_pzSurveyPage data page called from the ProcessUpdate data transform while creating the survey: this data page is for design time and should not be used at runtime as it requires design time pages like CaseTypePage which will not be available at runtime. To resolve this issue for runtime, in Step 3 of pzGetAllConnectors, pyClassName will be copied from the step page and set for pzGetConnectorsForDecision.

SR-120103 · Issue 183482

Headers auto-expanded when printing from portal

Resolved in Pega Version 7.1.8

When working on the classic portal (WorkUser), clicking the print icon was not automatically expanding the headers if they had been collapsed. This was an unintended behavior change, and the harness has been updated to restore the expected behavior.

SR-120103 · Issue 177698

Headers auto-expanded when printing from portal

Resolved in Pega Version 7.1.8

When working on the classic portal (WorkUser), clicking the print icon was not automatically expanding the headers if they had been collapsed. This was an unintended behavior change, and the harness has been updated to restore the expected behavior.

SR-123977 · Issue 185468

Optimized regex decision tree for property and when values

Resolved in Pega Version 7.1.8

A regex expression run against long property names was resulting in system slowdown and stuck requestor threads. A similar issue was encountered with When rules. To resolve this, the decision tree has been optimized.

SR-126181 · Issue 188742

Corrected tab display for failed visible when conditions

Resolved in Pega Version 7.1.8

When a repeating tab layout on a page group property includes "Body Visible When", tabs were displayed properly, but sections within were not being rendered for some tabs. To correct this, a visible when rule has been added to the outside content Div to handle situations where the when condition is not satisfied.

INC-185847 · Issue 669526

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.7

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

SR-122409 · Issue 182081

Refresh when active' tabs no longer affecting other tabs

Resolved in Pega Version 7.1.8

A tab using the 'Refresh when active' setting, could cause the content of other non auto refreshing tabs to re-execute. E.g. Report Definitions that are sourcing repeat grids in other tabs. This occurred when using the 'Refresh when active' setting on a tab whose content is a Dynamic Layout (the out-of-the-box default when adding a tab) with an embedded section. There was a local workaround of updating tabs to use the required section as the top level content rather than using a dynamic layout with an embedded section, and this has now been incorporated into the software. The refresh when active setting is still available in this configuration.

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