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-A18905 · Issue 233955

OrgName error resolved for MobileOffline:Obj-Open-By-Handle

Resolved in Pega Version 7.2.1

If Obj-Open-By-Handle was configured on the Org Name link in MobileOffline for the master details of a Contact Work Object, clicking on the link generated an "Empty Work Item Handle" error despite the OrganizationID(Handle) being present on the data page. This was an error in the actions array for the "runScript" API, and has been fixed.

SR-A21298 · Issue 239141

NPE on mobile list open resolved

Resolved in Pega Version 7.2.1

A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.

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.

SR-A24787 · Issue 247535

SA mobile app hang fixed

Resolved in Pega Version 7.2.1

Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.

SR-A24787 · Issue 245849

SA mobile app hang fixed

Resolved in Pega Version 7.2.1

Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.

INC-139861 · Issue 594006

Cross-site scripting protections added to Case Email

Resolved in Pega Version 8.5.4

Cross-site scripting updates have been added to rules handling linked email correspondence.

INC-155640 · Issue 622978

Mobile logging updated for data page required parameters

Resolved in Pega Version 8.5.4

After upgrade, the number of warnings increased substantially in the mobile app log file for D_Pages, specifying "Required parameter X for data page X cannot be blank." This was traced to the forced logging related to missing required parameters for Parameterized DataPages during DeltaSyncs. In order to increase the value of the logging, the process has been moved from being called before packaging the Data Page to being printed later in packaging code and set to warn only about any unsupported data page configuration with required parameters.

INC-157217 · Issue 631970

Field Service mobile refresh timing updated

Resolved in Pega Version 8.5.4

A configuration in the Field Service mobile app used to select and map data from a modal section to a wrapper section used "pega.fsm.mobileutil.reloadSection" to refresh the wrapper section and make the data visible after the mapping. If the refresh was performed after the initial login, the refresh was done on only a portion of the screen and resulted in incorrect data being shown to the user. However, continuing to fill in the section and then saving and reopening the task displayed the correct results. The issue was reproducible only on the first attempt after clearing cache/date: subsequent uses refreshed properly. This was traced to the timing of the configured actions, which caused the refreshSection action to be triggered before the runDataTransform action execution was completed. This has been resolved by adding code that will pause the action queue until the runDataTransform action completed.

INC-157532 · Issue 631715

Corrected runtime name length check for custom fields to resolve logged error

Resolved in Pega Version 8.5.4

The error "Notification_MobilePush.Action ERROR - Can't parse JSON string to map" was being frequently logged. Investigation showed that in the Step8 activity in pySendNofication from Pega-Notification-MobilePush class, setting @String.length(customFields)>0 where customFields was a local value caused the runtime length check on customFields to fail. To resolve this, the Step8 activity in pySendNofication from Pega-Notification-MobilePush class has been modified from using @String.length(customFields)>0 to use @String.length(Local.customFields)>0.

INC-160275 · Issue 628104

Unchecked Include descendant classes in pyFeedUserDetails report definition

Resolved in Pega Version 8.5.4

After upgrade from Pega 7.4. to Pega 8.4, the use of a custom class 'XX-Data-OperatorLoginDetails' which pattern-inherits from Data-Admin-Operator-ID was causing the error "Union not applied because properties [pyImageFileName, pyEmailAddress, pyUseLocale, pyDefaultTimeZone] are not optimized in Data-OperatorLoginDetails”. This happened when the case manager portal was launched and the report definition pyFeedUserDetails (introduced in newer releases) was running by default, and was due to the presence of a few unoptimized properties when the report definition had "Report on Descendant classes" - include all descendant classes, checked by default. To resolve this, the checkbox to Include descendant classes in pyFeedUserDetails is now set as unchecked by default.

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