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-D53139 · Issue 516511

ExposeCols supports running serially

Resolved in Pega Version 8.1.8

MSSQL can be prone to deadlocking, causing potential issues with ExposeCols (column population and index generation) which defaulted to multi-threaded. To resolve this, the system has been updated to allow configuration of ExposeCols to run serially: the properties expose.commitRate, expose.numOfThreads, and expose.batchsize in setupDatabase.xml ExposeCols executions, which were previously only available to prpcUtils, will be honored.

SR-D61094 · Issue 527341

Browser cache disabled to ensure fresh RAP file retrieval

Resolved in Pega Version 8.1.8

When using RAP download, reusing the same filename as a previous download caused the older file to be retrieved and not the newer version under that name. This was caused by RAP using the browser cache and downloading the same folder from service export directory. To resolve this, validation has been inserted to disable using the browser cache for the HTTP response.

SR-D63668 · Issue 525479

Access Control Policy updated to handle NotEqual with valuelist

Resolved in Pega Version 8.1.8

When editing the Access Control Policy Condition rule in Designer Studio and setting condition to 'is not equal', comparing it to a list generated the error "function not found". The same configuration worked as expected for the 'is equal' condition. This has been resolved by updating policycondition to handle a not equal scenario combined with a valueList property.

SR-D74848 · Issue 536998

Updated key handling for ProcessJWT

Resolved in Pega Version 8.1.8

After configuring an authentication service which used the ProcessJWT activity to validate the token received, the error "Unable to process the Json Web Token " was seen. Analysis showed the error was caused by a duplicate Key Id in JWK Endpoint Response: the system removed keys after processing, and in the case of duplicate keys the system was throwing null pointer exception because the key had already been removed. To resolve this, the system has been updated to not remove the keys from the map as part of this process.

SR-D76409 · Issue 540299

Cleanup added for staging directory

Resolved in Pega Version 8.1.8

Temporary files from imports and exports (from DevOps) were filling up the staging area disk space because there was no automatic process for cleaning up these local files. This has been resolved by adding an enhancement that will clear the directory on Engine Startup and any time ParUtils.setStagingDirectory gets called to initialize the staging directory.

SR-D78987 · Issue 544060

Support for custom jvm.args added

Resolved in Pega Version 8.1.8

In order to support Oracle PKI and other ticket based authentication, support has been added for custom jvm.args properties to setupDatabase and prpcUtils properties files.

SR-D79178 · Issue 543311

SameSite cookie setting added for Mashup support in Google Chrome v80+

Resolved in Pega Version 8.1.8

The Google Chrome browser version 80 and above now treats SameSite with a blank value as "Lax" by default, causing mashup scenarios to break. In order to compensate for this change, support has been added for setting SameSite=None in Cookie Settings; this value automatically includes the “secure” cookie flag, which enforces HTTPS for the Pega server and mashup. For mashups to work, SameSite should be set as None. Create a Dynamic system setting in the Pega-Engine RuleSet with the name “security/csrf/samesitecookieattributevalue” and the value "None" and restart the server. (The SameSite value "None" works only in secure HTTPS connections.) Note: The SameSite cookie may be set to None/Lax/Strict, based on the requirement. For cookie requirements other than mashup, it should be set as either Strict or Lax, depending upon your application.

SR-D68311 · Issue 535985

Corrected table row highlighting on iPad

Resolved in Pega Version 8.1.8

A table row was highlighted when clicked on an iPad in landscape view, but when the device was rotated to portrait view the row was not highlighted. This was traced to the background CSS overriding the selected style, and has been corrected by modifying py-responsive-overrides.css.

SR-D34359 · Issue 510602

StretchTabsWidth performance improvements

Resolved in Pega Version 8.1.8

Slowness was seen when a new intent task was created through an interaction. To improve performance, some of the unnecessary calls to the Layout Group _updateStretchTabsWidth() function have been eliminated, and the function code has been updated to use native javascript performant helper functions so it starts rendering sooner. A flag has also been added to disable addnewtab and resizeactions: these need to be enabled through pega.u.d.DISABLE_LG_RESIZE and pega.u.d.DISABLE_ADDNEWTAB.

SR-D43740 · Issue 512184

Added support for Helper Text Question Mark with visibility condition

Resolved in Pega Version 8.1.8

The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.

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