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-121183 · Issue 180073

Clarified complex visible 'when' usage with Expression Builder

Resolved in Pega Version 7.1.8

Execution was failing while using a complex visible 'when' expression with more than one Boolean operator. This is not incorrect behavior; Expression Builder only honors one Boolean operator, but the expression will work if typed directly and "Run on Client" is checked. This caused confusion due to the system not flagging the expression as unsupported in Expression Builder, and this has been fixed. In addition, the code has been updated to properly handle multiple logical operators so that runtime behavior is correct and no error is reported at save time. However, please note the following important information: For auto-generated sections, complex 'when' expressions will be allowed and honored when typed directly , but Expression Builders will still allow only one operator. Also, for non-auto generated sections and JSP directives, the old limitation of 1 operator will still apply.

INC-165992 · Issue 657691

Table Filter save uses correct harness

Resolved in Pega Version 8.7

After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.

INC-173760 · Issue 658069

Table Filter save uses correct harness

Resolved in Pega Version 8.7

After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.

SR-127517 · Issue 199062

Fixed Listview filtering using manual entry

Resolved in Pega Version 7.1.8

List View filtering was not working when the filter string was explicitly typed in the filter section. Handling has been added to the Embedded list filtering to correct this issue.

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

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.

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