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.

Decision Management

This release contains a number of fixes that improve the configuration and execution of Batch decisions – specifically, a number of usability improvements and addresses some issues when creating strategies on IE8.  

• Batch Decision functionality has been enhanced in the NBAM environment.
• In NBAM, users can run the strategy execution batch based on the Seed list class instead of the customer class. 
• Interaction data will now work even if Action or Organization  dimensions do not have values set.
• Running a strategy which includes a Data Import of a structured page reference will work in batch mode.
• Security was enhanced on the VBD Planner.
• The Access of Role to Object rules have been enhanced to allow users to create new Dimension Operator records.
• The NBAM Segment On Canvas will now fetch the SegMap data, even when the generated extended segment class has not been added to the Pages and Classes of the strategy.  The SegMap property will (if it exists) be added to a list of properties to fetch, even if the strategy indicates that it is not used.
• When a strategy is defined on a customer class, users may now specify the list of required properties to fetch for the input definition.
• When creating a new strategy, there is now a section to add a Strategy Results class like Business Issue or Group.

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.

New options to manage proposition validity

Manage your decisioning strategy more effectively with proposition validity settings. You can now set your propositions as always active, inactive, or active only within a defined time period. Setting a validity period for your propositions helps you to plan your strategy and automatically activate or deactivate propositions in the future.

For more information, see Proposition validity.

Device preview includes a configurable list of common mobile devices

Pega Express device preview displays your application in a simulated mobile device. By previewing your application, you can view the user experience on a desktop, tablet, or phone. You can select from a list of common devices or add devices to the list by editing Pega-DevicePreview-Device.

For more information, see Previewing an application on a mobile device.

Define adaptive model context

You can define model identifiers in the Adaptive Model rule instance, which serve as partitioning keys, by selecting properties from the top-level SR class of your application. The Adaptive Decision Manager (ADM) server uses model identifiers to create adaptive models that use the same configuration, but collect different adaptive statistics. Use model identifiers in the Adaptive Model rule to create adaptive models for your purposes.

For more information, see the Context tab on the Adaptive Model form.

DSM rulesets become part of the PegaRULES application

The Pega-DecisionArchitect, Pega-DecisionEngine, Pega-BigData, and Pega-NLP rulesets were moved from the PegaDM application record to the PegaRULES application record. This change makes decision management functionality available for Pega 7 Platform users by default without any additional configuration required.

For more information, see DSM rulesets become part of the PegaRULES application.