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-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 .

SR-120103 · Issue 183482

Headers auto-expanded when printing from portal

Resolved in Pega Version 7.1.8

When working on the classic portal (WorkUser), clicking the print icon was not automatically expanding the headers if they had been collapsed. This was an unintended behavior change, and the harness has been updated to restore the expected behavior.

SR-120103 · Issue 177698

Headers auto-expanded when printing from portal

Resolved in Pega Version 7.1.8

When working on the classic portal (WorkUser), clicking the print icon was not automatically expanding the headers if they had been collapsed. This was an unintended behavior change, and the harness has been updated to restore the expected behavior.

SR-120195 · Issue 180041

Smoothed adding rows to a repeat grid after canceling previous action

Resolved in Pega Version 7.1.8

When adding an item to the Repeat Grid, a small modal is opened to allow value entry to associate with that row. However, canceling the modal and then clicking on the button to add a row failed to open the modal a second time and it was not possible to add another row to the Repeat Grid. This was caused by the previous canceled modal call remaining active resulting in the new event being skipped. To correct this, the modal dialog incall property will be reset so it may be properly opened as expected following a previous cancelation.

SR-120218 · Issue 180532

Corrected dismissal of discard/cancel modal popup

Resolved in Pega Version 7.1.8

The out-of-the-box discard and cancel modal pop up was not closing up on single click. This was caused by a redundant action from the pyNewCaseHeaderInner section that has now been removed.

SR-120224 · Issue 178688

Potential vulnerability closed in XML stream generation

Resolved in Pega Version 7.1.8

A potential security issue was found with the XML stream generation and runtime, and has been corrected.

SR-120276 · Issue 179709

Corrected handling for DecimalPrecision Property Qualifiers in Advanced tab

Resolved in Pega Version 7.1.8

When DecimalPrecision Property Qualifiers were added to Advanced tabs, the Min/Max character limitation was not working for numeric input (Decimal) in pxTextInput or pxNumber. This was caused by an error in the initialization, and has been corrected.

SR-120324 · Issue 179256

Corrected DateTime controls in GroupBy

Resolved in Pega Version 7.1.8

Specifying any of the DateTime-* controls (e.g., DateTime-Short) in the Format field of the Group By property in a summary view was not working with the out-of-the-box settings; the DateTime property would be displayed in DateTime (GMT) format. This was found to be a field name hard coded to a value with a data type of text, causing the selected control to be ineffective, and has been changed.

SR-120329 · Issue 178133

Assembler compatibility issue resolved

Resolved in Pega Version 7.1.8

After upgrade, web services that modify the Header were failing due to a compatibility issue with the default assembler. While there was a workaround of giving the value of 'true' to the dynamic system settings 'Owning ruleset: Pega-IntegrationEngine' and 'Setting purpose: switchtooldassembler', this has been resolved.

SR-120381 · Issue 179868

TopLevelClass updated to accept a hyphen in the name

Resolved in Pega Version 7.1.8

Previously, the new application wizard Top-Level class did not support the use of a dash between two ruleset classes. An enhancement has been added to allow this format.

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