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.

INC-155406 · Issue 638706

Clipboard security updated

Resolved in Pega Version 8.7

Security has been enhanced for clipboard properties by restricting registration for readonly properties.

INC-157367 · Issue 637948

PDF generation corrected

Resolved in Pega Version 8.7

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-157448 · Issue 638925

Latitude and longitude populated for CreateWork history

Resolved in Pega Version 8.7

After enabling geo location in the casetype rule, when the case was created using the Create menu option from either Dev studio or Manager portal the Latitude and longitude values were set on the pxRequestor page and were available in the Case Audit history in the Map control. When the same case was created using CreateWork action configured on a button, it did not log the latitude and longitude values in the case Audit history. Investigation showed this was caused by a 'when' condition in the AddWorkHistory activity which checks the requestor page for latitude value and which had a null value when a createWork action was used to create the case. To correct this, the template metadata of the form will be populated with latitude and longitude values from pxRequestor page to be used in the latitude and longitude hidden fields.

INC-160805 · Issue 640854

PDF generation corrected

Resolved in Pega Version 8.7

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-160839 · Issue 643470

Session timer corrected

Resolved in Pega Version 8.7

Configuring pxsessiontimer in the Portal header to log users off after 30 minutes was not working as expected: users were still logged in the next day or after keeping the session idle for more than 30 minutes. After waking up the system, it was possible to search clicking on the search results resulted in being logged out. This was traced to the ShowLogoffTimer activity not being correctly registered, and has been resolved.

INC-161480 · Issue 629627

Confirmation button works on dirty alert

Resolved in Pega Version 8.7

The "Ok" button on the discard changes alert was not working. This has been corrected.

INC-161937 · Issue 640264

VMWare workspace One Mobile support added

Resolved in Pega Version 8.7

Support has been added for the VMWare workspace One Mobile app by updating the BrowserUtilsRuntime file to add the necessary user agent.

INC-162426 · Issue 638771

Regex handling updated for Rich Text Editor spellcheck

Resolved in Pega Version 8.7

When using the Rich Text Editor and performing a spell check, the spell checker was adding additional CSS to the property. This was traced to the presence of a unicode newline character causing the existing regex to fail to strip the style tags. To resolve this, regex handling for the unicode newline character in the style tag has been added.

INC-163198 · Issue 637798

Performance improvements for research path interaction

Resolved in Pega Version 8.7

Research path interaction driver composite loading was taking an excessive amount of time due to RULE-HTML-SECTION @BASECLASS ERRORLIST being called multiple times. This has been resolved by changing the ErrorList Section to guard the getMessagesMapByEntryHandle API call with a condition "if (ClipboardPage.getMessageCountAll > 0)".

INC-163544 · Issue 639301

Accessibility corrected for Cosmos user portal left navigation panel

Resolved in Pega Version 8.7

It was not possible to see the focused control label in the left pane of the Cosmos user portal because it was not expanding when its control received focus from tabbing. Investigation showed the class acting as a polyfill for :focus-within was applied only on the observed element when using Microsoft Explorer 11, and this has been resolved by updating the CSS selectors and ensuring the class is applied to every parent element down the DOM tree.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us