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.

Show multiple views of data in your application

You can now show multiple views of data in your application by adding the record editor (pxRecordsEditor) section to a layout, another section, or a cell in a layout. You can configure the section to customize the display and enable the search, import, and export capabilities of the record editor.

For more information, see Multiple views of data in the record editor section.

Support for additional rule types for PegaUnit test cases

To compare the expected results with the results that are returned by running a rule, you can now create PegaUnit test cases for the following rule types:

• Activities
• Data transforms
• Strategies
• Decision trees
• Decision tables

After you unit test these rules, you can convert them to test cases and configure assertions on the test cases. You can also set up the clipboard with data before tests are run, and clean up the clipboard after tests are run.

For more information, see PegaUnit testing.

Page assertions are supported for PegaUnit test cases

You can now create page assertions for PegaUnit test cases. Because data transforms and activities can create or remove pages, you can configure page assertions to determine whether a page exists after you run PegaUnit test cases.

For more information, see Configuring page assertions.

Authenticate REST data sources by using OAuth 2.0

You can now authenticate the data sources that are created from your REST integration by configuring OAuth 2.0 authentication in the New REST Integration wizard. You can specify or create an OAuth 2.0 authentication profile in the wizard by using the client credentials or authorization code grant type.

For more information, see OAuth 2.0 in REST integration.

Customized data imports

You can now further customize the data import process in Data Designer by:

• Setting a default import purpose and preventing the selection of an import purpose to speed up frequent imports of the same kind
• Removing the import purposes that you do not need for your data type
• Defining a default field mapping between the fields in the .csv file and the fields in your data type that act as a unique identifier (key), to save time during the import process
• Skipping the import progress screen and showing progress contextually within your application
• Including the link for data import anywhere in your application or calling it in the background from a service or agent

For more information, see Data import customization.

Enhanced data imports

The data import process in Data Designer has been enhanced to give you more options. You can now import case types, save and use templates for field mapping, add data without updating existing data, specify date and time formats, and reprocess erroneous records by downloading a .csv file that lists the errors in your data import. You can also adjust the data import wizard to the context where it is included.

For more information, see Data import enhancements. 

Pega File Listener process changes

Beginning with Pega 7.2.2, File Listener processes files in a different way:

• File movement in directories – Previously, files were processed from the Work directory. In Pega 7.2.2, files are processed from the source location. Files move to the Work directory only if the initial processing fails and Recovery is disabled.
• New file processing – Previously, File Listener would process all files in the source location, even if the files were added during the processing. In Pega 7.2.2, files added to the source location during processing are read the next time the File Listener starts.

For more information, see File Listener data instances.