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.

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.

Derby databases are no longer supported

Previously, an embedded Derby database could be used as a file system. This setup was configured by setting storage/class/<<filesystem>>/type to "embedded" in the prconfig file.

After upgrading, storage types that are specified as "embedded" now default to the local file system.

Configuration required for data operations on external schema when using a Postgres database

When you use the API for data operations on external schema in the Postgres database, you must update the prconfig.xml file. No other platform requires a prconfig.xml update.

To update the prconfig.xml file:

1. Stop the server and add the following entry to the prconfig.xml file:
   env name="database/databases/postgres_ext/defaultSchema"
   value="externalschema"
   where postgres_ext is the external database that uses the external schema “externalschema”.
2. Restart the server.