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-C5015 · Issue 362314

Passivated queue cleared for dismissed window

Resolved in Pega Version 8.1

If there were open active tabs in the portal work space and the window was closed with the browser 'close' icon instead of logging off, the active threads related to that session were not properly terminated and would reappear if the browser window was reopened. The system has now been updated to ensure that the queue will be properly cleared in this scenario when using <env name="Initialization/PersistRequestor" value="Never"/>.

SR-C5022 · Issue 354557

Check added to Optimized Locking for assignmentkey

Resolved in Pega Version 8.1

When two users tried to acquire an assignment at same time in a system using Optimistic locking, an assignment processing error occurred. This was traced to the assignment key validation not being done while checking for ValidAssignment. When Optimistic locking is used, a prompt is shown to the current user working on the assignment if another user opened and worked on the same assignment simultaneously. A refresh button is shown to resolve conflicts and show the review harness. Existing logic takes care of completion of an assignment, but in this case the assignment is the same but has moved from workbasket to worklist. On click of Refresh, 'RefreshOnConflicts" is checking with the existing change logic and since assignment still exists it was trying to preformAssignment with the old assignmentkey(workbasket) which is not valid. To correct this, a new condition has been added to RefreshOnConflicts in the Pega-ProcessEngine ruleset to check if existing assignment is valid or not. If it's not a valid assignment, the system will open the review harness rather than processing the assignment.

SR-C50325 · Issue 390099

null pointer exception fixed for clearing table column filters

Resolved in Pega Version 8.1

A NullPointerException was generated when clicking on the Clear Filter link after filtering a column in a table. This was traced to an error in the pzGetGridColUniqueValues step 4 'when' condition that caused it to always be false. This has been fixed.

SR-C5053 · Issue 353680

Static assembly will exclude withdrawn rules

Resolved in Pega Version 8.1

When performing the Agile Studio installation step of running the static assembly, there were 20 rules that failed to build. The log file showed a number of rules that were withdrawn that were being selected for assembly in ApplicationAssembly, and this was traced to the SQL query used to gather the rules not excluding rules with an availability of "Withdrawn" or "No". This has been corrected so withdrawn rules will not be selected.

SR-C50636 · Issue 389298

JSON data flow export updated to not include pxObjClass

Resolved in Pega Version 8.1

Previously, the Data set used to provide option to select which properties should be populated in the JSON file. This option was removed recently, but when Convert Shape was used in the data flow to populate only required properties, the pxObjClass was is always passed to the JSON file and caused an error with the consuming application which was not able to support it. To resolve this, the pxObjClass attribute will be excluded from JSON export for HDFS and File DS, and an option to exclude a set of properties was added to ClipboardPageJsonConverter.

SR-C50638 · Issue 390148

Non-standard JVM heap size argument removed and replaced with more generic max-mem

Resolved in Pega Version 8.1

The IBM JVM was not honoring the MaxHeapSize property, causing installs/upgrade on Java 8 with the IBM JVM to fail unless an alternate max memory was provided. To resolve this, the usage of a non-standard heap size argument has been removed and replaced with a more generic max-mem present within the master for all JVMs to take advantage of. At the same time, the default memory and space requirements have been reduced as prpcServiceUtils now needs less than it previously did.

SR-C50728 · Issue 391340

Added handling to save page list properties of all text

Resolved in Pega Version 8.1

After creating page list properties to display the text input on a case, the input data was not saved properly If all the page list properties were text. Investigation showed that instead of saving the entered input, the system was saving the last property value to all the fields from the pagelist because the "pyCellId" being generated was the same for all the cells in grid row. This has been corrected by setting the pyCellId to pyFieldId from the Embed-Field object and using the unique hash for pyFieldId that is set so that they match.

SR-C50990 · Issue 391318

Bypass added to handle custom S3-compatible repositories

Resolved in Pega Version 8.1

While saving a newly created S3-compatible custom Data-Repository rule instance, the exception "Save failed - Unknown Repository Type :Embed-Repository-Type-Custom-S3Compatible" exception was generated. This has been resolved with the addition of the proper bypasses so custom repositories are not registered the same way as standard ones.

SR-C51065 · Issue 390587

Corrected unexpected date error for imported propositions

Resolved in Pega Version 8.1

While importing a proposition with a specific start date and end date, even though the start and end dates are valid the error: "Start date should be prior to end date" appeared. This has been corrected with code that will convert the start and end dates before comparing them in pyPostCSVUpload activity.

SR-C51065 · Issue 390653

Corrected unexpected date error for imported propositions

Resolved in Pega Version 8.1

While importing a proposition with a specific start date and end date, even though the start and end dates are valid the error: "Start date should be prior to end date" appeared. This has been corrected with code that will convert the start and end dates before comparing them in pyPostCSVUpload activity.

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