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-182423 · Issue 691800

Pull to refresh disabled during case submission

Resolved in Pega Version 8.6.3

Triggering a refresh (swipe down) on mobile while the spinning loading indicator was shown resulted in the error 'This action is not allowed' instead of being able to view the case. This has been resolved by disabling pull to refresh when there is any background network activity in progress.

INC-183485 · Issue 692519

ClientCache performance optimization

Resolved in Pega Version 8.6.3

In order to improve performance for the mobile app, updates have been made to optimize the ClientCache list interations.

INC-185434 · Issue 674054

Page group property passed correctly for complex questions

Resolved in Pega Version 8.6.3

When the Pega Survey Smart shape was used to configure a list of complex set of questions using Question rules and invoked using the Survey shape, the reload system was not passing the subscript value for the Page group property pyQuestionnaire. This caused an Invalid Reference exception and displayed an error pop up for the end user. Investigation traced this to a call to RefreshList to load a section holding pyQuestionnaire(Subscript) page content which was in place as part of a legacy fix but which has since been made unnecessary due to infrastructure changes in the DOM utilities. To resolve this, the ComplexQuestionCheckboxTemplate and pzComplexQuestionCheckBoxTemplateRowDetails section rules have been updated to remove the RefreshList action on checkbox.

INC-187230 · Issue 672473

Resolved exception during LDP processing

Resolved in Pega Version 8.6.3

A ConcurrentModificationException was appearing during the processing of Large Data Pages. This has been resolved with the addition of a lock on clear method in ConcurrentReplicatedPage.

INC-189511 · Issue 679185

Column width adjusted for Survey simple question text area

Resolved in Pega Version 8.6.3

When a number of columns were entered in a simple question (Answer tab) for a text area, the width was not reduced or increased for the text area. This has been resolved by setting pySpecifyWidth to custom for textarea.

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