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.

SR-D29127 · Issue 506863

SAML data pages restored after passivation

Resolved in Pega Version 8.2.4

If login used SAML SSO, resuming the session after passivation resulted in missing or empty data pages when using an SAP integration with Pega Cloud. This was traced to a security change that modified the D_SAMLAssertionDataPage and D_SamlSsoLoginInfo data pages as readonly, causing them to not be passivated under these conditions. To resolve this, the data pages have been made editable so they will be restored as expected. This change also resolves any difficulty with SAML logoff activities in conjunction with SAP and Pega Cloud.

SR-B84336 · Issue 332037

onOnlineDetected use matches documentation

Resolved in Pega Version 7.4

iOS11 was failing the first login attempt. Documentation for the addListener method in pzPega_offline_datasync rule lists 'onOnlineDetected' as optional, but when the listener was added without onOnlineDetected the console.error occurred. This was originally a documentation error where the rule was incorrectly given as optional even though the event handlers always assumed onOnlineDetected was defined, but as there are reasons to support this use the system has been updated this so onOnlineDetected is truly optional now.

SR-B95350 · Issue 341577

Rollbacks use CreateDateTime for ordering list

Resolved in Pega Version 7.4

When processing a rollback for multiple hotfixes, the system was retrieving a list of uncommitted hotfixes from the database without specifying any order and, as a result sometimes the item were in the correct (i.e. reverse of installed) order and sometimes not. This was the unintended consequence of switching to using generated unique IDs which do not maintain any ordering, and has been fixed by modifying the process of retrieving the uncommitted hotfixes list to provide descending ordering based on pxCreateDateTime.

SR-B67903 · Issue 329428

Fix for Data Transform when Clipboard Page not found.

Resolved in Pega Version 7.4

Logic has been added to correct the scope references of the generated offline-Datatransform-JS when using AppendAndMapTo.

SR-B67903 · Issue 328792

Fix for Data Transform when Clipboard Page not found.

Resolved in Pega Version 7.4

Logic has been added to correct the scope references of the generated offline-Datatransform-JS when using AppendAndMapTo.

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-B94506 · Issue 341185

Unneeded clipboard use cleared during sync

Resolved in Pega Version 7.4

During the "delta sync" process, a very large clipboard size (96 MB) was observed for offline sync service requestors. Further analysis showed that the application page contained a property pyOfflineCases which increased the application page size from 28K to 679K. Since the property isn't present in the saved application rule model, the pzDataSyncPackager rule will clear it from the clipboard to improve performance.

INC-173162 · Issue 650795

Certificate match will use Subject Distinguished Name

Resolved in Pega Version 8.7

Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.

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