Word merge support with Microsoft Silverlight plug-in
Valid from Pega Version 7.1.3
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.
Integration
Valid from Pega Version 7.1.4
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
Valid from Pega Version 7.1.3
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
Valid from Pega Version 7.1.3
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.
Improved data page performance
Valid from Pega Version 8.4
Data pages that are sourced from report definitions now support server-side paging. This functionality optimizes the performance and memory of data pages, making them more efficient at retrieving large lists of data. In addition to getting page indicators at the top of a grid, you can sort and filter columns in a grid in conjunction with paging. If you want the system to use server-side pagination, you can also enable pagination from the Data page rule form.
For more information, see Defining data page access.
Email supports Microsoft Graph
Valid from Pega Version 8.4
Email integration with Microsoft Office 365 now supports Microsoft Graph. By using Microsoft Graph, you can process inbound email more securely and avoid using less secure protocols, such as IMAP and POP3.
For more information, see Creating an email account.
Email listener enhancements for faster email processing
Valid from Pega Version 8.4
Enhanced email listeners now process more emails in less time. To increase throughput, you can configure email listeners to process several emails simultaneously, instead of one at a time.
For more information, see Creating an email listener.
Support for data page aggregation
Valid from Pega Version 8.4
You can now aggregate data from multiple sources for faster and easier implementations. With this feature, you can load data pages more easily without using an activity or data transform.
For more information, see Creating a data page.
Improved contracts for implementations
Valid from Pega Version 8.4
For more complete contracts, automations now support embedded pages, default values, and picklists. These enhancements provide a more robust model for inputs and outputs that is easier to update and maintain.
For more information, see Viewing automations.
Enhanced OpenAPI Specification generation
Valid from Pega Version 8.4
To better understand the purpose of your REST API, you can now generate a more complete OpenAPI Specification (OAS) from REST service rules in Pega Platform™. The system uses relevant records to build an accurate schema definition for page and page list outputs, and generate stronger schema type definitions for all inputs, outputs, and fields, such as array
or boolean
. You can also generate OAS by mapping values to JSON or Clipboard in the request, or mapping values from JSON or Clipboard in the response.
For more information, see Service REST rules.