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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C30790 · Issue 370354

Work Pages merged to preserve data during failed sync

Resolved in Pega Version 8.1

An issue was seen where there was data loss when an offline case failed SYNC. When a sync issue happens while processing the actions, the case is moved to the configured error sync work basket or the default work basket. The last instance of the pyWorkPage of the failed case is kept as it will have all the data up to the point of the failed assignment. However, after the pyWorkPage diff changed, the system was sending only the changed data. That meant when a sync error happened only the pyWorkPage of the last failed assignment was saved and all the data submitted in the earlier actions was lost. The system has now been updated to merge all the pyWorkPages sent in the action corresponding to same Work Object via the new pzMergeClientWorkPages activity which will call the pzMoveToSyncWorkBasket activity.

SR-C30799 · Issue 376199

XSL transform while opening clipboard fixed for WebSphere

Resolved in Pega Version 8.1

While opening a clipboard from a user profile an exception was generated in the tracer. This was traced to an XSL transform on a particular IBM WebSphere server resulting in conflicting JARs for the XLS transformation and has been resolved by modifying ProcessXSLT RUF to remove the setAttribute for 'http://javax.xml.XMLConstants/property/accessExternalDTD'.

SR-C30808 · Issue 371553

REST Integration Wizard logic modified to resolve Null Pointer Exception

Resolved in Pega Version 8.1

When the sample request / response data for the REST Data Source Wizard contained a parameter that started with at least one character that was not valid for a Property name and the next two characters after the illegal character removal were "px" or "pz", then the system attempted to make a new Property record with a name that starts with one of the "reserved prefixes" (px, pz). That attempt was blocked. The illegal name was then also patterned over into rules related to the Property, causing them to be invalid due to their relationship with a nonexistent Property record. The Wizard was then forced to stop generating records and roll back the changes. To correct this issue, the "Property name cleaning" logic has been replaced with new logic that can handle the "illegal characters followed by px or pz" use-case.When RuleGeneratorCommon is creating a new MappingPropertyInfo, it will call the new 2-argument flavor of RuleGeneratorUtils.normalizePropertyName(...). This new normalization method performs the property-specific cleaning (removing prefixes) as the last step. RuleGeneratorCommon is also used to attempt to remove prefixes before all other formatting is performed.

SR-C31053 · Issue 372867

Added null check for CurrentAssignmentPage

Resolved in Pega Version 8.1

If a CurrentAssignmentPage was null on the first OpenAssignmentAction, the application would constantly spin. This has been fixed by properly initializing the currentAssignmentPage in the onHaveAssignment method instead of onHaveWorkObject of openAssignmentAction and by adding a null check to evaluate whether the object is needed and should be reinitialized.

SR-C31086 · Issue 371965

Scanner now supports hotfixes with only Rule-RuleSet-* instances

Resolved in Pega Version 8.1

Previously, the Scanner bypassed Rule-RuleSet-* instances, causing an issue where a hotfix that contained only these instances generated an exception indicating an ambiguous status and the hotfix could not be installed. This has been corrected by modifying the Scanner to now consider all rules valid for scanning.

SR-C31109 · Issue 377026

Handling added to clear dashboard Data pages and thread when switching activity

Resolved in Pega Version 8.1

After publishing a dashboard to an application, everything worked as expected when directly logging into that application. However, if the user had multiple access groups and switched to another access group, the wrong dashboard was displayed and D_pxUserDashboardLoadList was not reloaded. This has been resolved by moving the D_pxUserDashboardLoadList Data page to Thread level and adding the new Data transform PZCLEARDASHBOARDDATAPAGES called from pzClearDataPagesBeforeSwitch. This will clear the dashboard Datapages and the thread when switching the activity.

SR-C3119 · Issue 383017

Fixed CSRF token issue for enableWhitelistReferrer

Resolved in Pega Version 8.1

An issue was found with Checking in / deleting a rule when the setting security/csrf/enableWhitelistReferrer was set to false. This was caused by a CSRF token issue, and has been fixed by comparing with it to the token of the parent thread if lookup by current thread fails.

SR-C31307 · Issue 377219

Attachment saved to external storage retains new name

Resolved in Pega Version 8.1

When files were saved in external web storage (configured via app definition "Integration & Security tab), an attachment name that was changed from the default was reverting to the default name when attached again. Handling has now been added to pzSaveToWebStorage to retain the override name for the file.

SR-C31307 · Issue 355606

Attachment saved to external storage retains new name

Resolved in Pega Version 8.1

When files were saved in external web storage (configured via app definition "Integration & Security tab), an attachment name that was changed from the default was reverting to the default name when attached again. Handling has now been added to pzSaveToWebStorage to retain the override name for the file.

SR-C31469 · Issue 371885

PageList properties for List assertion resolve to correct class

Resolved in Pega Version 8.1

Errors indicating "pyStepPage can not be empty for List card" occurred when attempting to save Strategy related Test cases. This was traced to the system not not resolving to the correct class instance type when loading PageList properties for List assertion in strategy related Test cases, and has been corrected.

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