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-B39878 · Issue 299678

Fixed encoding of colon for exported report title

Resolved in Pega Version 7.3

A file exported using Chrome or Mozilla displayed %3A instead of Underscore (_) when replacing a colon in the title. This was an error in the encoding, and has been fixed.

SR-B40038 · Issue 298378

Column alignment with filter icon fixed for Chrome and IE

Resolved in Pega Version 7.3

When a grid was configured with filtering and 'Freeze Grid Header' option was enabled, at runtime the column header did not align as expected with the filter icon when using Chrome or IE. In IE, the anchor element for filter icon needs to have height set to render properly. In Chrome, the oflowDiv gets a height which caused the problem. To resolve the issue, the addHeightToFilterIcon function in ui_grid JS has been modified to consider freeze header cases.

SR-B40059 · Issue 296152

IACAuthentication security improved

Resolved in Pega Version 7.3

The IACAuthentication activity assumed third party authentication and did not check for a password. In order to improve security, default password validation has been added to the shipped IACAuthentication activity.

SR-B40144 · Issue 297046

Facebook Connector queries updated

Resolved in Pega Version 7.3

The default queries used to harvest private messages in Facebook Connector have been updated to match changes made by Facebook.

SR-B40177 · Issue 297056

Resolved harness error after using pagination 'load more'

Resolved in Pega Version 7.3

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

SR-B40267 · Issue 298233

Decimal comma handling added to VBDServiceImpl for all locales

Resolved in Pega Version 7.3

A NumberFormatException was thrown when executing a VBD query on a server configured with a Locale that uses the decimal comma instead of the decimal point. This caused launch failure for the Offer flow from the Pega Marketing Portal. The issue originated with the decimal format for time calculation for elapsed time in seconds in not being handled in VBDServiceImpl for all Locales, and has been fixed.

SR-B40310 · Issue 299601

Offline sync fixed for post-processing Question shape

Resolved in Pega Version 7.3

The post-processing activity of a Question shape was not skipped when 'only execute post processing on client' was checked on the case type rule. A 'when' condition has been added for the post processing activity of Question Flow to fix this.

SR-B40310 · Issue 299855

Offline sync fixed for post-processing Question shape

Resolved in Pega Version 7.3

The post-processing activity of a Question shape was not skipped when 'only execute post processing on client' was checked on the case type rule. A 'when' condition has been added for the post processing activity of Question Flow to fix this.

SR-B4047 · Issue 276127

Fixed intermittent drag and drop failure in List to List with IE

Resolved in Pega Version 7.3

After double-clicking an item in Internet Explorer to move it from left to right in 'List to List' control, the drag and drop functionality intermittently stopped working. This was due to the listeners being removed after double clicking or scrolling and again clicking, and code has been added to reattach the event listeners.

SR-B40657 · Issue 298764

Clarified database privileges to start Pega

Resolved in Pega Version 7.3

The documentation has been updated for clarity regarding database privileges for start up. The text "Pegasystems recommends that you create an Admin user separate from the Base user; however, if you opt for a single Base user, grant these permissions to the Base user" has been modified to read: "Pegasystems recommends that you create an Admin user separate from the Base user; however, if you opt for a single Base user, grant the Base user both sets of privileges listed above."

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