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-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-119812 · Issue 178547

Added logic to more precisely determine class of referred properties within repeating grids

Resolved in Pega Version 7.1.8

In some work flow scenarios with referring properties within repeating grids, Work Class properties were being returned when Collateral Data Class properties were expected. This was caused by an incomplete reference call within the grid, and the logic has been updated to set the class of a grid on the server to call a new function that parses the property given as a source and determines what its class is.

SR-119899 · Issue 177532

Breadcrumb functionality disabled for Process Modeler pending further development

Resolved in Pega Version 7.1.8

Some complex installations experienced OOM events and crashes when opening flows in Process Modeler that contained nested levels of nested sub flows. The root cause of this problem was code that allowed excess data to be opened into the clipboard for every sub flow that could potentially be run as a result of running the top level flow. To prevent this problem, breadcrumbs functionality has been disabled at this time. The canvas viewer is being rewritten for ML9 together with a new implementation of multi-level process navigation in order to resolve this issue.

SR-119899 · Issue 182818

Breadcrumb functionality disabled for Process Modeler pending further development

Resolved in Pega Version 7.1.8

Some complex installations experienced OOM events and crashes when opening flows in Process Modeler that contained nested levels of nested sub flows. The root cause of this problem was code that allowed excess data to be opened into the clipboard for every sub flow that could potentially be run as a result of running the top level flow. To prevent this problem, breadcrumbs functionality has been disabled at this time. The canvas viewer is being rewritten for ML9 together with a new implementation of multi-level process navigation in order to resolve this issue.

SR-119920 · Issue 176644

Radio button display corrected for IOS8

Resolved in Pega Version 7.1.8

When the filter pop up menu was launched in IOS8 Mobile, the selectable radio buttons were mis-aligned while scrolling a RepeatGrid. To resolve this, changes have been made to ui_grid.CSS.

SR-119963 · Issue 176108

Corrected record imports in multitenant environment

Resolved in Pega Version 7.1.8

In the multitenant environment, reimporting an operator record using application -> import was causing an 'IntegrityConstraintViolationException' exception. This was caused by the query not being properly tenant-qualified for the environment, and has been corrected.

SR-119978 · Issue 184032

Corrected handling for properties in XML rule

Resolved in Pega Version 7.1.8

When using properties mapped on the root element of an XML SOAP rule, the attributes were mapped properly but the element value was not. In a related error, after giving ParseXML rule invocation values for Type Substitution for Parse XML, the XML was not mapped to the clipboard for the type substituted elements. There was a workaround of using DSS 'switchtooldassembler', but this has been fixed by updating parsexmlsaxrulewrapper.

SR-120018 · Issue 182167

Handling improved for additional clicks during Report Definition processing

Resolved in Pega Version 7.1.8

When a Report Definition is used on a grid with filters on some columns, it is possible to click on filter and enter some value there. If there is huge data array, it takes some time for filter to load. If there is a click somewhere else in the grid while the filter is loading, the UI became unresponsive. In order to improve performance, a check has been inserted to verify the status of an asynchronous request and handle it smoothly.

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.

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