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-127180 · Issue 192478

Modified display of Listview filters to show action buttons

Resolved in Pega Version 7.1.8

After upgrading, Listviews used to generate reports that included filtering were not displaying the "Apply" and "Cancel" buttons in the drill-down pop up. To resolve this, the setscrollingDIVHeight API has been modified to properly display the content.

SR-127202 · Issue 192389

Join and Like filters tuned for Listview

Resolved in Pega Version 7.1.8

Listview join filters with LIKE operations were not performing optimal SQL queries, impacting system performance. This has been tuned to improve the system response.

SR-127237 · Issue 190840

Time-related RUFs now use operator's time zone

Resolved in Pega Version 7.1.8

Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone

SR-127237 · Issue 189891

Time-related RUFs now use operator's time zone

Resolved in Pega Version 7.1.8

Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone

SR-127517 · Issue 199062

Fixed Listview filtering using manual entry

Resolved in Pega Version 7.1.8

List View filtering was not working when the filter string was explicitly typed in the filter section. Handling has been added to the Embedded list filtering to correct this issue.

SR-127549 · Issue 190837

Improved processing of WSDL for the Create SOAP Integration wizard

Resolved in Pega Version 7.1.8

When running the Create Soap Integration wizard for a selected operation from the WSDL, the wizard was not only generating the necessary rules for the selected operation, but for all operations in the WSDL. To address this, when processTypeContentsAndRelatives is processing a parent type, it now skips type substitutions of the parent.

SR-127743 · Issue 193331

Trace rule servicetype set for Service-File

Resolved in Pega Version 7.1.8

'Trace rule' for the Service-File is not working even though 'Trace rule' for Pega Service type worked correctly. This was caused by an inability to trace the Service-File due to not setting the servicetype, and the API has been updated to explicitly set the servicetype as "File" in ServiceAPI class.

SR-127829 · Issue 192723

Magnifying glass popup fixed for XML-stream element mapping data

Resolved in Pega Version 7.1.8

After importing XSD through the Connector and Metadata Wizard, double-clicking on an element-mapping to bring up the magnifying glass popup returned the error "Unable to open the rule as Base Class Value is empty". This was traced to a recent change that converted Ruleforms from form-based to harness-based, and OpenRuleAdvanced control has been modified to handle the XML stream information correctly.

SR-127853 · Issue 193472

Locking updated for hidden elements in Data Type records

Resolved in Pega Version 7.1.8

If Data Type records were being edited, the lock on the row being edited was not released unless a change was made. This led to locks being left over once the operator has closed the Data Type and other operators were prevented from editing those rows. The problem was that change tracking was not getting invoked for the hidden elements present in the section for each row, and this has been added.

SR-127853 · Issue 193468

Locking updated for hidden elements in Data Type records

Resolved in Pega Version 7.1.8

If Data Type records were being edited, the lock on the row being edited was not released unless a change was made. This led to locks being left over once the operator has closed the Data Type and other operators were prevented from editing those rows. The problem was that change tracking was not getting invoked for the hidden elements present in the section for each row, and this has been added.

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