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.

SR-117345 · Issue 179910

"Edit in Excel" handling corrected for delegated decision tables

Resolved in Pega Version 7.1.8

"Edit in Excel" was not working correctly on a decision table if it was delegated to a WorkManager portal from a traditional portal. After clicking on the edit button two pop ups appeared, and the Excel sheet was not visible after the pop ups were dismissed. This was traced to an issue with ActiveX where the server was not getting a fully-qualified URL in cases of open portal threads, and a check has been added to ensure proper handling.

SR-117931 · Issue 181714

Resolved clipboard conflict for obj-open-by-handle

Resolved in Pega Version 7.1.8

Doing an obj-open-by-handle or obj-open-by-handle/copy on work objects containing properties that reference data pages caused errors about non modifiable pxObjClass properties and non matching clipboard property modes. This was caused by a clipboard conflict, and has been addressed by handling the clipboard property as set value for feature property.

SR-118440 · Issue 178175

Sorting fixed for RD Repeat Grids with joined properties

Resolved in Pega Version 7.1.8

When sorting a Repeat Grid based on a Report Definition, if the user tries to sort on a property from a join then it would fail with the error 'Cannot get property information for: Assign-Worklist..' This was caused by ObjClass being missing for few elements of page list, and has been fixed. In addition, a check has been added to ensure proper handling in cases where Obj class is missing.

SR-118474 · Issue 182925

Corrected time zone mismatch in Report Browser

Resolved in Pega Version 7.1.8

If a server and an operator had different time zones set, reports that were scheduled through the report browser to run and deliver notifications to a list of recipients would run immediately if the schedule was modified. To handle this time zone difference, "Pega-ScheduledTask.pzPostProcess" has been modified to use the time zone from calendar in the formatter.

SR-118474 · Issue 178295

Corrected time zone mismatch in Report Browser

Resolved in Pega Version 7.1.8

If a server and an operator had different time zones set, reports that were scheduled through the report browser to run and deliver notifications to a list of recipients would run immediately if the schedule was modified. To handle this time zone difference, "Pega-ScheduledTask.pzPostProcess" has been modified to use the time zone from calendar in the formatter.

SR-118755 · Issue 177568

Enhanced logging for access group decisions

Resolved in Pega Version 7.1.8

In order to facilitate troubleshooting, logging has been added to track how the Core Engine decides what Access Group to assign to the running Agent. This lists the name/ruleset/ruleset version of the Data-Agent-Queue record being utilized, the Access Group specified by it, and any further steps that determine what AG gets used. If the DAQ gets rebuilt, it will show how it gets rebuilt from the Rule-Agent-Queue record.

SR-119707 · Issue 178023

All results shown by default for database searches

Resolved in Pega Version 7.1.8

Previously, when performing a database search by using the "old:" keyword prefix and some of the results were removed by the pyTransform activity due to the number of matches exceeding the Initial Results Limit, the "Show All Results" option would not appear in the footer information. This behavior has been changed and such commands will automatically search and display all results.

SR-119800 · Issue 177840

Security policy transaction mismatch error resolved

Resolved in Pega Version 7.1.8

If security policies are enabled, logging out and then logging in prompts a password change. If the password was changed and then the page was refreshed, a transaction mismatch error occurred. This was caused by incomplete clearing of the password setting transaction, and the system has been updated to properly switch transactions.

SR-119810 · Issue 178693

Filtering options removed for RepeatGrid columns to ensure consistent results

Resolved in Pega Version 7.1.8

When creating a RepeatGrid with Filtering option enabled, applying the filter on the JUSTIFMicrosoft Internet ExplorerD? field's True/False property was returning variable results in the Application Guardrails "All Warnings" report depending on whether the column filter was set to JUSTIFMicrosoft Internet ExplorerD NO or JUSTIFICATION was left blank (the top choice on the filter dropdown). This was found to be an issue where toggling the filter criteria wasn't filtering out the warnings from rules residing in Pega- rulesets. Until this can be properly addressed within the application's scope, the filtering option on columns has been removed.

SR-120083 · Issue 179048

Expression Builder updated to suggest proper value tokens

Resolved in Pega Version 7.1.8

When defining an input column in a Decision Table rule to evaluate the result of an expression, the Expression Builder suggested that the token '' could be used to plug in the value from the current row of the column into an expression. This was an incorrect recommendation, and would not return the correct values. The correct token to use is . This error was due to the JavaGenerateAPIVersion property missing in the rule data after Rule-form was upgraded to Harness. This property is used to determine the substitute keyword ( or ) based on the version, and is present to support or upgrade decision table for work flow rules prior to 05-02-01. It does not impact the functionality of the feature, but has been changed to give the correct suggestion for .

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