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-213918 · Issue 714452

Discard button works consistently

Resolved in Pega Version 8.7.2

After check out, the discard button was not working consistently for decision tables or MapValue. Investigation showed this occurred when an exported file was being downloaded in the same window, as the thread would be busy with the file and not able to perform the discard action on the window. To resolve this, the configuration for the download on the same window has been removed, exportToDecisionTable has been modified to handle an iframe, and a runScript action has been added to register the exportToExcel activity and download in iframe.

INC-216935 · Issue 714047

Corrected decision table scroll bar display in resized section

Resolved in Pega Version 8.7.2

Resizing a decision table window was causing the horizontal scroll bar to move out of the section while scrolling. This has been resolved by updating the HTML and adding the needed CSS.

INC-217991 · Issue 714331

Display of 'check all' check box made configurable

Resolved in Pega Version 8.7.2

A new overridable 'when' rule pyShowSelectAllCBInSurvey has been added to allow customizing a survey to hide the 'Select all' checkbox in the ComplexQuestionCheckboxTemplate section.

INC-192649 · Issue 706133

Basereference context available for attach content control

Resolved in Pega Version 8.7.2

An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.

INC-195601 · Issue 685770

Basereference context available for attach content control

Resolved in Pega Version 8.7.2

An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.

INC-198249 · Issue 705092

Security updates for packaging mobile app

Resolved in Pega Version 8.7.2

Unsafe properties such as password and userId are now explicitly filtered from the Operator object during the mobile app packaging process.

INC-201633 · Issue 706556

Reload icon disappears when refresh is ready

Resolved in Pega Version 8.7.2

After updating the Field Service Mobile App from Pega 8.3 to Pega 8.6, the wait icon continued to be visible even after the refresh was completed. This has been resolved.

INC-210526 · Issue 705639

Mobile supports icons for file attachment

Resolved in Pega Version 8.7.2

Attaching a file to a case in a mobile browser generated a script error popup. This has been resolved with code to support using icons to attach files on mobile.

INC-211208 · Issue 709647

Added fallback handling for missing Google Maps marker value

Resolved in Pega Version 8.7.2

The Google maps location position control was not showing the marker if the marker source was a Property. No issues were seen if a data page was used as the marker source. This was due to the pega.util. Dom.getElementsByName(markerPropertyHandle) being returned as null. Since the property value was not found in DOM, the latitude and longitude values were not resolved for the marker object. This has been resolved by relying on the markerPropertyValue as a fallback in case the property bound to the marker is not part of the DOM.

INC-214160 · Issue 709282

Access group context handling updated for Mobile

Resolved in Pega Version 8.7.2

After update, a new mobile application for a specific access group was not applying the correct access group for an operator with multiple access groups but instead used the default access group. This has been resolved by moving the logic responsible for switching access groups for Pega Mobile Client from the Authorization.getInitialAccessGroup class to the SessionAccessgroupInfo class to ensure Authorization/SessionAuthorization gets the information about the default access group for the current context.

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