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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-C68993 · Issue 416162

Expression exngine correctly evaluates boolean type property with expression

Resolved in Pega Version 8.3

Expression exngine correctly evaluates boolean type property with expression When using a dynamic layout with a visibility condition expression and 'Run Visibility Condition on client' checked, a condition such as .VehicleDetails != '' && .VehicleDetails = true was not being evaluated as expected after upgrade. This issue was related to changes made to the expression engine to get the initial evaluation result at the server side, and was caused by a missed use case for a boolean type property with expression. This has been corrected.

SR-C68069 · Issue 416697

Page group use added to referenced properties context for RDL

Resolved in Pega Version 8.3

After upgrade, a stack mismatch error was generated by a previously-working configuration that used a nested RDL with a section under Work- class that itself contained an RDL with Data- property that then included a section from Data -- class which contained another RDL that referred to the Work- Page Group. This error was caused by the use case of page group being missed during implementation of referenced properties in ContextProcessor processListNode, which has now been resolved.

SR-C71043 · Issue 416761

pzSendEmail returned to revious behavior of sending separate emails to work parties

Resolved in Pega Version 8.3

After upgrade, a change in behavior was seen when using the pzSendEmail activity. When pzSendEmail was called to send emails to work parties, a single email is sent to all recipients instead of separate emails to each recipient as it did in earlier versions. The SendSimpleEmail activity accepts a SendDiscreteMails parameter, but the pzSendEmail activity had 'Pass current parameter page' checked so the default value for the SendDiscreteMails parameter was not used. This was a backwards compatibility error, and has been corrected by setting the SendDiscreteMails parameter to true by default in the pzSendEmail activity.

SR-C75397 · Issue 417291

Handling added for empty UILabel in grid fields

Resolved in Pega Version 8.3

When using a Datetime property with a default format, opening the filter popup and clicking on the 'select all' check box caused the format of the values to break. This was traced to ".pyUILabel" being passed as empty, and handling has been added for that in "pzUniqueValuesGridFields".

SR-C80050 · Issue 417605

Schema name made consistent for DDL generation

Resolved in Pega Version 8.3

A platform upgrade failed if there were application schemas configured with a table configuration that specified a schema other than the rules schema. This was an issue caused by the generated DDL having the incorrect schema name for the table due to the name being hard-coded in the Data-Admin-DB-Table entry definition. The system was using this schema name to find the table and generate the correct changes, but the SQL statement used the table from the database connection instead of the override. When the XML that represents the difference between the "source" and "target" state is generated, the system is supposed to replace the schema name with the target schema name. However, if the source schema name is blank that step was skipped in order to defer to the connection for shipped tables. In order to ensure that the system can generate the correct DDL and complete the upgrade, the system will now always replace the schema name regardless of the source or target value.

SR-C74677 · Issue 418338

ADM pulse timing changed to inprove performance on very large clusters

Resolved in Pega Version 8.3

ADM uses a pulse that checks if any models need to be updated. This uses a Cassandra query which has no "where" clause, causing poor performance for very large clusters. For immediate relief of this issue, the pulse configuration has been updated to increase the timing from 30 to 300 seconds so it fires less often. Model updates typically happen every x hours and often the pulse will not detect any models that would need to be updated. Further improvements in this process will be available in a future release.

SR-C76995 · Issue 418701

CSV import for delete date values will be formatted before row processing

Resolved in Pega Version 8.3

In order to support using CSV import for delete purposes, date/time class keys will be formatted before processing the row.

SR-C75205 · Issue 418808

Invalid text entry in Date control field now returns current timestamp

Resolved in Pega Version 8.3

Inconsistent behavior was seen between entering an invalid date in numeric vs text format. Entering an invalid date in number format resulted in the system replacing the entered value with the text “Invalid date”. Entering an invalid date in text format caused the system to retain the value and not show a validation error. This has been corrected by modifying the date/time formatting for both text and numerical input to return the timestamp in case the entered value is incorrect.

SR-C80076 · Issue 419093

Added check before deleting pxObjClass to avoid agent runtime exceptions

Resolved in Pega Version 8.3

When the rule was not assembled, agents were failing with exceptions. During label control assembly execution, standard attributes for label assembly including pxObjClass are removed from the cell page. There is a catch for the exception during cell trimming for browser requests, but the customer agent was failing because UnmodifiablePropertyException is a runtime exception that sets the step status to fail. This has been fixed by adding a check when attempting to delete a property from Clipboard page: if the property is pxObjClass, it will not be deleted.

SR-C66675 · Issue 419142

5 cross-site scripting security added to Multiselect controls

Resolved in Pega Version 8.3

Multiselect controls have been updated for greater cross-site scripting security.

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