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-D17919 · Issue 491580

Corrected thread switching when moving between interactions tabs

Resolved in Pega Version 8.2.3

When using Create New for a Phone Call-Consumer in one tab and Create New for an Outbound Phone Call on another tab, the thread was not changing when switching between the tabs of the interactions. Closing the Outbound call interaction resulted in null pages on the clipboard. This has been resolved by updating the pzpega_ui_doc_tabsupport file so it switches to root document context if called from onActivate function using a flag.

SR-D17973 · Issue 489738

Corected parameter mismatch to allow deletes to be added to history

Resolved in Pega Version 8.2.3

Pega was not keeping track of a property if it was deleted from the data explorer tab, resulting in not being able to restore the deleted property. This was traced to a parameter mismatch: the Delete API adds the Memo parameter to the history, but while DeleteRecord accepted the Memo parameter, DeleteRecordInner accepted the HistoryMemo parameter. Because the parameters names were different, they were not propagated to the API. This has been corrected by setting the param.memo so that Rule-Delete API adds the history and the rule gets displayed correctly in recently deleted rules.

SR-D18200 · Issue 492098

Whitelist security added to getDataPage API

Resolved in Pega Version 8.2.3

In order to secure data pages that may be exposed through using Global Resource Settings with the pega.api.ui.actions.getDataPage API, logic has been added to expose only mentioned data pages from the clipboard through pyPublicDataPageWhiteList.

SR-D18809 · Issue 490872

Localization added to SetCMISMessageWarning

Resolved in Pega Version 8.2.3

Localization has been added to pzSetCMISManageWarning for the warning message "This attachment is locked for editing by you".

SR-D18907 · Issue 488898

Property references now supported for label and checkbox captions

Resolved in Pega Version 8.2.3

An enhancement has been added to support the use of a property reference for labels and checkbox captions.

SR-D18960 · Issue 499910

Logic updated to resolve busy indicator delay

Resolved in Pega Version 8.2.3

On click of submit in the main interaction flow, the busy indicator was not getting displayed or was displayed after a delay whenever there were a series of Ajax requests being made. The logic has been updated to resolve this issue.

SR-D19083 · Issue 490401

Autocomplete list resets to top of scroll if selected data is deleted from the control

Resolved in Pega Version 8.2.3

If an autocomplete on Screen did not initially have any input, pressing the down arrow showed the popover data with the scrollbar on the top. Scrolling down and selecting an item from the autocomplete suggestions and then tabbing out closed the popover. If the data was then deleted from the control and the down arrow was pressed again, the popover suggestion showed the data in the last scrolled position instead of restarting from the top as expected. Investigation showed that when autocomplete used a list configuration, the popover div was not being updated if the data was deleted from the control. This has been corrected.

SR-D19177 · Issue 492339

Mashup refined to not trigger resize from popup

Resolved in Pega Version 8.2.3

The parent window was being refreshed when an action was performed on the child window or the child window was resized from the mashup script. This has been resolved by altering the logic to avoid triggering resize from popups in a mashup scenario.

SR-D19602 · Issue 489988

GetDirections API enhanced to send exact current location to Google Maps

Resolved in Pega Version 8.2.3

The GetDirections API was not fetching the exact current location for Google Maps. In order to enhance precision, selecting the current location will use the navigation.geolocation.getCurrentPosition API to get the latitude and longitude position and send it as a saddr parameter to Google Maps.

SR-D19821 · Issue 490065

Resolved UI styling for layout group with 'run visibility on client'

Resolved in Pega Version 8.2.3

UI styling for Layout Group(Tab) was not working, resulting in the border/background color not being saved for layout groups. This was traced to a scenario where the same property was present in both the "Header" and "Tabs" settings of the layout group and "run visibility on client" was checked for the header, enabling the property at runtime. This has been resolved by modifying pyHeader in "Embed-Skin-Component-LayoutGroup" to uncheck "Run visibility condition on client".

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