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-D55160 · Issue 520356

Namibia and Botswana added to Currency Symbol values

Resolved in Pega Version 8.1.8

Support has been added for the Namibia (en_NA) and Botswana (en_BW) locales in the default Currency Symbol values.

SR-D56527 · Issue 538302

DSS PegaAESREmote*ResetTableStats set to false

Resolved in Pega Version 8.1.8

In order to prevent an issue with resetting table stats that potentially impacts postgres in an unintended fashion, the DSS PegaAESREmote*ResetTableStats has been set to false.

SR-D57038 · Issue 519381

JobScheduler DST handling updated

Resolved in Pega Version 8.1.8

When the locale being used changed out of Daylight Savings Time, scheduled jobs did run at the same local time as before but instead ran an hour earlier than expected. Investigation showed that jobscheduler calculated the next runtime based on the time difference from the cluster reference time and current time in milliseconds, and this offset in milliseconds was added to next run time. Since the cluster was started in DST, the job was running on same time due to the time difference. To resolve this, the system will use a calculation offset and set hours/minutes to nextRunTime object so that calendar lib handles daylight savings.

SR-D58927 · Issue 522289

Added expiration for orphaned tracers

Resolved in Pega Version 8.1.8

After tracing a REST service, the tracer was persisting but not showing in the requestor list from Admin studio. The operator shown in the error did not have access to the system anymore, and other users were not able to trace the service rule. Trying to clear the requestors in all the nodes using API POST /nodes/{nodeID}/pools/requestor/clear also did not resolve the issue. To address this, a distributed rule watch expiration has been added.

SR-D83192 · Issue 545056

JobScheduler DST handling updated

Resolved in Pega Version 8.1.8

When the locale being used changed out of Daylight Savings Time, scheduled jobs did run at the same local time as before but instead ran an hour earlier than expected. Investigation showed that jobscheduler calculated the next runtime based on the time difference from the cluster reference time and current time in milliseconds, and this offset in milliseconds was added to next run time. Since the cluster was started in DST, the job was running on same time due to the time difference. To resolve this, the system will use a calculation offset and set hours/minutes to nextRunTime object so that calendar lib handles daylight savings.

SR-D37317 · Issue 518893

Run Ruleset Cleanup defaults to true

Resolved in Pega Version 8.1.8

After upgrade, the rule categories and rules were not showing correctly in the App view of the Dev Portal. Many warning messages were also logged related to the Decisioning DM Sample application. This was traced to the rules cleanup script not running properly. While there was a workaround of applying the ruleset cleanup scripts manually after removing the queries that reference the pr_engineclasses table, the cleanup will now be set to run by default (run.ruleset.cleanup=true). In addition, the logic to determine which RuleSets to include has been simplified and most of the pr4_rule_vw deletions have been combined.

SR-D46681 · Issue 514435

SnapStart supports SAML2 Authentication

Resolved in Pega Version 8.1.8

When using an HTTP Post to SnapStart into Pega using PRCustom style or PRAuth style SAML authentication, the login was looping back to the login request. Investigation showed that the Pega ACS was posting data properly back to the RelayState URL, however the login activity was not getting the SAMLResponse and simply sent a SAML Login Request again. This has been fixed by updating reqContextURI in case of SAML2 Authentication service so pyActivity=value will be passed.

SR-D48762 · Issue 518297

Enhancement added to support DB2 CREATE OR REPLACE view syntax

Resolved in Pega Version 8.1.8

After creating the product, attempting to import it on another environment failed due to incompatibilities with the syntax. In SQLGeneratorDb2.getViewSourceStatement(), when the View definition is fetched there is a check whether the view starts with "CREATE VIEW". Since the customer view of "CREATE OR REPLACE" was not supported in Db2LUW, it didn't match and appended the "CREATE VIEW" statement again. This happened only when using DB2, and has been resolved by updating the logic in SQLGeneratorDb2.getViewSourceStatement() to support CREATE OR REPLACE VIEW statements.

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.

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