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-160485 · Issue 655297

Trailing "/" added to public links for SSO use

Resolved in Pega Version 8.7

Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it.

INC-178148 · Issue 660924

Handling added for SSO servlet name

Resolved in Pega Version 8.7

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

INC-188405 · Issue 673063

Handling added for SSO servlet name

Resolved in Pega Version 8.7

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

INC-195519 · Issue 698497

Support added for using CFW when Pega server is unavailable

Resolved in Pega Version 8.7.1

Data synchronization changes have been added to allow Client for Windows to work in offline mode without an AppCache manifest.

INC-180184 · Issue 665091

Assistance and diagnostics added for issue with opening imported 'when'

Resolved in Pega Version 8.7

After upgrade, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.

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-A14781 · Issue 246050

Timeout value honored for ConnectSOAP using JMS Transport

Resolved in Pega Version 7.2.1

ConnectSOAP has a response timeout function, but this setting was not being honored when JMS transport was used. This has been corrected.

SR-A21636 · Issue 240162

Fixed auto-complete use in iPhone Opportunity creation

Resolved in Pega Version 7.2.1

Issues were seen when selecting items using Auto-Complete on an iPhone while creating an Opportunity. This was due to a positioning error in the logic, and has been fixed.

INC-189259 · Issue 674820

Big Decimal used while converting List to Page

Resolved in Pega Version 8.7

Previous work done to handle precision numbers in the JSON response that were being rounded or truncated when parsed for the DataSource page has been updated to also handle the case of mapping a list to a page.

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