Published Release Notes

Extended currency control

The currency control can now display a different currency than the locale currency. This means a user in one country can view amounts that are designated in a foreign currency, using that currency's international conventions.  For example, a credit card transaction in Germany might need to be posted in US dollars. 

Responsive layout groups and grids

The Responsive UI was introduced in Version 7.1, and has now been enhanced in two areas, to create an entirely responsive UI.

PRPC 7.1.4 introduces the Layout Group control, which can render its contents as “tabs,” “accordions,” or as a “menu.”  The rendering choice is driven through the presentation layout (the skin), which presents the information responsively:  a “tab” at a certain breakpoint can turn into an “accordion” or a dropdown-style menu, depending upon what format would be most appropriate for the device/screen size being used.

The grid functionality has also been enhanced, so that grids may be displayed on a tablet or a phone without the need for horizontal scrolling, offering the optimum experience on a mobile device.  A PRPC Grid Layout now supports responsive breakpoints in the skin definition in which columns can drop off or be consolidated according to screen size.

Designers will be able to mark columns in the grid by importance, and at the first breakpoint, the columns marked as “less important” will be dropped off first.  At the second breakpoint, the grid turns into a “fat list,” with the most important column displaying as a heading for each item in the “fat list.”  Styling options can be associated with these breakpoints.

Improved accessibility support

PRPC support for accessibility has been enhanced to allow applications to better meet the standards of the Web Content Accessibility Guidelines (WCAG), 2.0 AA. 

Input Method Editor (IME) support

PRPC has added support for the Microsoft Windows Input Method Editor (IME), to allow developers to enter complex characters in four different East Asian languages using the standard keyboard.  The IME is a way to create input using a keyboard, by using additional windows for character editing or selection, in order to facilitate entry of alternate writing systems.

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.

User Interface

This release had a focus around improving support for accessibility for all the PRPC UI Components as well as extending capabilities for responsive design with grids and tabs. A series of cosmetic changes and fixes are included.

• Improvements have been made for action items being opened in a dynamic container.
• Row repeat functionality in sections has been improved to better handle source properties.
• Screen layouts have been optimized for the iPhone platform
• The display on dynamic containers has been enhanced to provide the same behavior for both single-mode and multi-mode.
• The Launch Harness feature has been improved to launch into a pop-up window.
• The operator menu will now display from the Case Manager portal.
• The Primary Page functionality has been enhanced for control-defined Repeating Tab Headers.
• Using local actions defined as modal windows has been enhanced to work in an iPAD using a Safari browser.
• When using a modal dialog to open a flow action in a repeat grid, to add an item to the list, users may now cancel out of this dialog if no changes are needed.

Case-insensitive filtering in reports

Filtering in reports is now case-insensitive, improving the reporting and searching experience. You can turn off case-insensitive filtering, for example, by using an activity. You might want to do this if your index is too big or if the length of time it takes for indexing impacts performance.

For more information on report filtering, see Editing filter conditions.

PATCH support for REST integrations

REST connectors and REST services now include support for integrating with REST APIs that require using the PATCH method. REST integrations that support the PATCH method allow you to make partial updates to individual resources while retaining data that does not require an update. With PATCH support, you no longer need to write complex custom code to integrate with services that require using the PATCH method.

For more information about REST integrations, see Connect REST form - Completing the Methods tab.

Configure REST connectors for standard-compliant endpoints

REST connectors now support all standards-compliant endpoint URLs, regardless of how those URLs use query parameters.

This URL support allows you to do the following actions:

• Include repeated query string parameters in a URL.
• Omit a query string parameter if the value of the parameter is empty when you send a request.
• Apply appropriate encoding for different URL components.

For more information about REST connectors, see Connect REST form.