Published Release Notes

Use SAML 2.0 to provide single sign-on authentication

Configure a SAML 2.0 authentication service to provide web single sign-on (SSO) convenience to product users in your enterprise. A one-click option lets you import Identity Provider (IdP) metadata and make use of automated certificate management.

User interface distortions in the Decision Manager portal

By default, the New Application wizard in Pega 7.1.6 configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Decision Manager portal. Both applications created in previous maintenance level updates and applications created in Pega 7.1.6 that do not include the UI-Kit-7 dependency are not impacted by this known issue.

Workaround:

1. Open the application record.
2. In Application Rulesets, remove UI-Kit-7.
3. Save the application record.

User interface distortions in the Predictive Analytics Director portal

By default, the New Application wizard configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Predictive Analytics Director portal. Applications created in maintenance level updates previous to Pega 7.1.6, and applications that do not include the UI-Kit-7 dependency, are not impacted by this known issue.

Workaround:

1. Open the application record.
2. In Application Rulesets, remove UI-Kit-7.
3. Save the application record.

Add additional columns to customized work history tables

The standard work history table, pc_history_work, contains two new columns that return the latitude and longitude coordinate location of the action that prompted the history. Mobile devices can display this location as a street address. If you have a customized work history table, add these two columns to it:

• <decimal name="pxLatitude" size="19" scale="9"/>
• <decimal name="pxLongitude" size="19" scale="9"/>

Microsof Internet Explorer 9 (IE9) may display a script error when clicking a Help button

A script error may be displayed when clicking a Help button when script error notification is turned on in the browser. As a work around, uncheck the Display a notification about every script error option in the Advanced tab of the Options dialog box in Microsoft Internet Explorer 9.

Real-time event processing

Real-time event processing is a mechanism that can be used to analyze a high velocity stream of events entering the system and derive conclusions from them. It is possible to define metrics, measurements, and conditions under which subsequent trigger events are generated.

For details, see Real-time event processing.

End of support for form-based rule forms in Pega 7.1.9

Rule forms that are configured to render as forms are no longer supported in Designer Studio or end-user applications. Form-based configurations are found on custom rule types that were created in earlier versions of Pega 7 and are characterized by pop-up windows that are rendered externally from Designer Studio.

Reconfigure Pega 7 applications that use such rule forms by using standard harnesses and sections.

1. Open the class form.
2. Click the Advanced tab.
3. Select Harness from the Rule formmenu.
4. Create a new harness and new sections that implement the logic of the custom rule, using standard user interface layouts and controls.

Migrating custom rule forms to harnesses and sections offers the following benefits:

• User interfaces become HTML5 WC3 compatible and responsive to different screen sizes.
• User interfaces become cross-browser compatible, rendered consistently in Google Chrome, Mozilla Firefox, Apple Safari, and recent versions of Microsoft Internet Explorer.
• Rendering performance on modern browsers is dramatically improved.
• User interface pop-up behavior is eliminated; all windows are rendered inside Designer Studio and end-user applications.

End of support for Microsoft Internet Explorer 8 and quirks mode applications in Pega 7.1.9

In accordance with Microsoft’s announcement to discontinue support for Internet Explorer 8 in January 2016, Pega 7.1.9 does not support Internet Explorer 8, nor does it support non-HTML5 standard user interfaces.

You must upgrade to Microsoft Internet Explorer 9 or later or use Google Chrome, Apple Safari, or Mozilla Firefox. If you are using Internet Explorer 9 or later, you must turn off compatibility mode by accessing the Compatibility View settings.

Note the following:

• Pega 7.1.9 does not support user interface rules that are not based on HTML5 standards (rules in quirks mode).
• If you use applications that are rendered in quirks mode, which enables Pega 7 to correctly display and render non-HTML5 standard user interfaces, you must update them to standards-based HTML5 user interfaces when you upgrade to Pega 7.1.9 or later. Pega 7 provides automated tools to help you migrate your applications.
• Pegasystems Global Customer Support will not investigate or fix any Pega 7.1.9 bugs or support requests that are exclusive to Internet Explorer 8 or quirks mode user interfaces.

You can quickly identify which components of your application user interface are not HTML5 standards-based by clicking Designer Studio > User Interface > HTML5 Application Readiness.

Upgrading to Pega 7.1.9 and a newer browser offers the following benefits:

• These browsers are HTML5 and CSS3 compliant.
• New features are supported and existing features work as intended.
• The Pega 7 Platform user interface is displayed and rendered as intended.
• Browser security is enhanced.

If you have additional questions about browser support, see the Platform Support Guide or contact Pegasystems Global Customer Support.

Report Browser removed from Designer Studio

The Report Browser and Access landing page have been removed from Designer Studio. In Designer Studio, developers can create, edit, and test reports by using the Report Definition rule form.

The Report Browser is still available in the Case Manager portal.

Real-time pulse processing for multinode systems

Multinode development environments now use real-time pulse processing. Previously, when a change was made on one node, the pulse processing interval could take a minute or more for that change to be reflected on another node. Now, when a rule is changed on one node, that change is immediately reflected on all the other nodes in the cluster. This change helps to ensure that users are running a rule on the same node as where the rule was changed.