Published Release Notes

Integration

Critical customer-driven product improvements were made to SOAP services, SOAP connectors and connector wizard, CMIS connectors, and the Pega Image Viewer. These fixes addressed a handful of functionality gaps discovered in PRPC 7.1 and earlier releases by internal and external customers.

• A Connect-CMIS instance which was created using a reference to an ATOM Server Instance may now use Global Resource Settings.
• The Execute Synchronously (one-way operation) has been enhanced for SOAP Services.
• The Silverlight version of PegaImageViewer has been enhanced to print ranges of multiple pages at once.
• The SOAP Wizard has been improved to show all the ports which are available in the WSDL file.
• Two way SSL has been enhanced for the Connect-REST rule.

Reporting & Data

This release fixed many existing unlocalizable elements in 7.1 reporting interfaces (The Report Viewer, Report Editor, Chart Editor, and the Report Browser) and now they are fully localizable. Changes were made to make Listview, summaryview,  and report viewer display possible WCAG 2.0 level A and AA support.

• Parameters may now be used in a sub-report join condition.
• Report Definition localization has been enhanced.
• Standalone ListViews with embedded SmartInfo have been improved to resize appropriately when the SmartInfo section is expanded.
• The data section of a report will now display in all of the available space when a fixed header option is selected.
• When localizing a listview with filters, tool tips are translated.

Data Management

Improvements to data handling were made for the Data Pages, autopopulate properties, and reference properties.  Lightweight lists were optimized.

• Property references are now maintained on the Work Page.
• PageList properties can reference a Data Page.
• Auto-populate properties can be used in a seciton to show results from a Data Page.
• Data Pages can run in “Page” mode as well as “List” mode
• The "Rules Not Using Lightweight List" report was enhanced.
• A PageList property that references a Data Page may be used to populate a grid.
• Related autopopulated properties can now be referenced.

Integration

Usability enhancements have been made to the integration wizards. The REST end-point integration has been improved, and XML parsing functionality has been enhanced.

• PRPC services can return Report or Listview data as XML.
• Work items may now be processed when accessing from a link in system-created emails.
• An SMTP outage will not cause an application to stop working.
• File listener will now read files using a leading asterisk (*).
• XML Parse rule will handle schema validation.
• PegaImageViewer will now work with Version 7.1.
• Security measures are enhanced for SOAP connections to web services.
• After generating rules using REST wizard, the Undo Generation button will delete all the generated rules.
• Email wizard has been improved.

Reporting

This release had a focus on extending key capabilities to improve the functionality and ease of use of reporting features based on early adopter feedback.  A series of cosmetic changes and fixes are also included.

• Multiple boxes may be checked on List view checkboxes
• Dashboard Charts slider has been improved.
• Summary View reports and charts have been enhanced.
• Column properties can be added to a report in the Report Editor.
• List view column widths can be set by Smart Info.
• Listviews will display correctly for updated systems.
• Improvements to the GuardRail Report.

Improvements to support Kibana log viewing

Pega® Cloud resolved a known infrastructure error that prevented customers in AP-southeast-2 region from properly viewing their log messages in Kibana.

Pega Cloud introduced this enhancement as of QI 2018.

New dynamic setting to manage validation of hidden fields

Pega Platform™ version 8.6.4 introduces a new DSS setting for Theme Cosmos and other section-based applications. The validateHiddenField setting controls whether the application validates fields that you hide through visibility rules. By default, validateHiddenField is set to true, which means that the application fields are validated for completeness even if they are not displayed in the form. You can also switch off this functionality by changing the setting value to false. 

For more information, see Managing field validation in hidden sections.