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-199354 · Issue 696718

Corrected pulse comments rendering in mobile

Resolved in Pega Version 8.7.1

When using mobile, clicking the number on the Pulse comments section was not responding and conversations inside a comment were not visible. This has been resolved by updating pypega.social.js and pypega.social.css so the section renders correctly.

INC-197410 · Issue 690216

Handling added for invalid numeric range

Resolved in Pega Version 8.7.1

When filtering the range in number column with value as “1000000” , the validation message appeared as "1000000 : This results in an invalid numeric range". This has been resolved with an update to use Data-value to get the non-formatted value for decimal.

INC-182874 · Issue 675311

Update Language Pack for correct direct web access link localization

Resolved in Pega Version 8.7.1

When a direct web access (DWA) link was generated for an external user to perform an action on an external assignment, the shared link was corrupted when used with localization on the receiving system. This was due to the JSP fragment in the correspondence not being properly translated during localization. To resolve this, please access the most recent Language Pack available from https://community.pega.com/marketplace/language-packs/pega-platform

INC-195321 · Issue 684971

Check added for readonly header control

Resolved in Pega Version 8.7.1

After configuring an optimized grid and adding a checkbox control in the header with editable options, when the control in corresponding column was configured as Auto, the checkbox in the header was rendered as read-only. When the control in the corresponding column was configured as "Read-only always" or displayText control was used, the checkbox was rendered as editable control. This was traced to a missing check for pyEditOptions = "Read-only", and has ben resolved.

INC-200237 · Issue 693179

Added API for Pega Call Team websocket reconnect

Resolved in Pega Version 8.7.1

When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.

INC-187617 · Issue 692543

Added API for Pega Call Team websocket reconnect

Resolved in Pega Version 8.7.1

When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.

INC-189748 · Issue 694737

Added API for Pega Call Team websocket reconnect

Resolved in Pega Version 8.7.1

When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.

SR-C80753 · Issue 419246

Native calendar control works for Firefox on Android

Resolved in Pega Version 8.2

When using Firefox with 'Use native control on mobile' checked, attempting to enter a date into the DateTime field highlighted the mm field but the date selector did not open and keyboard entry was not recognized. This was traced to the native calendar for date time control not opening in Firefox on Android. To correct this, type checks for date, time and datetime-local have been added to the isTextBox function in pzpega_ui_events_infra js.

SR-C62412 · Issue 402624

VBD enhancements added to assist in cleanup

Resolved in Pega Version 8.2

Running VBD for a long period of time will lead to accumulating partition summaries without a safe means to clean up. Enhancements have now been added to support the following:1) An API has been added to VBDService to support deletion of partitions from cache AND persistence prior to a date. This can be used as a building block for "keep last X days" functionality on a VBD dataset. 2) The Start Date will be used when loading Partition summary data when the service initially loads. Eviction logic has been implemented to remove partitions along with summary data (e.g. counts and dictionaries) for partition keys earlier than Start Date. Eviction occurs when Start Date moves ahead of partition's timestamp. If Start Date is updated backward by user and there exists data in Cassandra on these dates, then the partition summaries should be loaded into the cache. This requires a full cache reload which will be automatically triggered.

INC-199341 · Issue 694712

Content-type values made consistent

Resolved in Pega Version 8.7.1

The content-type for service APIs was returned as 'text' for 401 errors when using a custom authentication type instead of the parent-type/child-type format such as text/plain, text/html, application/json, etc. This has been corrected.

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