Published Release Notes

Word merge support with Microsoft Silverlight plug-in

PRPC features that integrate with the Word merge capability are now cross-browser. ActiveX controls (which are only compatible with IE) have been replaced with Microsoft Silverlight. This plug-in must be downloaded separately from Microsoft, as it is not shipped with PRPC.

Some common PRPC features affected by this change include the Application Document Wizard, App Profile, Specifications Landing Page, Specification form, and Case Type Landing Page.

Prior to using these features, Users of PRPC 7.1.3 need to set up their client system(s) as follows:

1. Install Silverlight plug-in

Follow the PRPC prompt to install Silverlight when you attempt to use the Word merge feature:

Or download package directly: www.microsoft.com/silverlight/

2. Install PRPC prerequisites

Microsoft Internet Explorer (IE) browsers automatically detect the need for PRPC prerequisites and will prompt for install:

Non-IE browsers will load a pop-up window when the user attempts to use the Word merge feature.  Use the link to manually download PRPC prerequisites:

Extract the .zip file, execute setup.exe and follow the install wizard:

Administrators setting up multiple clients at once may refer to the pzSLpreReqs.cab available in the PRPC 7.1.3 resource kit.

3. Restart browser

Log out of PRPC, close all open sessions and restart your browser.

The PRPC feature integrated with Word merge is now ready for use; Silverlight prompts are no longer displayed.

4. Troubleshooting

Silverlight installation requires access to your file system and a registry setting update to “trust” the associated Verisign certificate.  Contact your administrator if you encounter any security or permission errors during this process.

See the PRPC Developer Help for more information on browser setup requirements.

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.

Support for sending emails by using Microsoft Graph

Email integration with Microsoft Office 365 now supports sending emails by using Microsoft Graph. With this enhancement, you can send email with a more secure protocol that complies with your organization’s security policy.

For more information, see Creating an email account.

Support for REST connectors to route network traffic via proxy

To easily route network traffic, you can now configure proxy details for individual REST connectors. This enhancement allows you to manage your proxy settings so that you can securely access online resources that lie beyond your proxy servers.

For more information, see Configuring a REST connector.

Connect-HTTP support discontinued

Pega Platform™ no longer supports Connect-HTTP rules. HTTP connectors were used to start HTTP request/response interactions between Pega Platform and external systems identified by a Connect HTTP rule (Rule-Connect-HTTP rule type).

After an upgrade to Pega Platform 8.6 and later, you can still use and modify existing HTTP connectors, but you cannot create new ones. As a best practice, use REST connectors instead, which offer more capabilities and have better support from development teams.

For more information, see Connect REST rules.

Data import wizard compatibility with Cosmos applications

The data import wizard is now Cosmos-compliant. When you launch the data import wizard as a page, you can leverage the new features provided by Theme-Cosmos, such as adding custom buttons and functionality to your Cosmos applications.

Support for configuring and saving external data in App Studio

You can now configure a savable data plan to easily replace or update related data directly from App Studio, and persist those changes during the case lifecycle. This enhancement allows you to work directly in App Studio, without being limited to read-only access of data from case types.

Automation performance enhancements

To improve the performance of automation-based REST services and DX APIs, you can now configure JSON inputs and outputs in automation rules. The automation passes the JSON object directly to an automation-based REST service or DX API, eliminating the need to transform data on a page to JSON first. You can also take advantage of this enhancement if you are calling an automation from an activity. Additionally, you can simulate a JSON response in the automation rule and update the JSON sample if needed.

For more information, see <link TBD> and <link TBD>.

Support for creating automations

You can now create automations in Pega Platform. By creating an automation, you clearly define a contract to perform a specific task. For example, you can create an automation that retrieves a list of data objects that are available in the application.  

For more information, see Creating an automation.