Published Release Notes

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.

Text analytics on the Pega 7 Platform

The Pega 7 Platform offers users the capability to analyze units of text, extract quality information, and translate it into business intelligence. The text analytics functionality aims to determine the positive, negative, and neutral polarities (tone) of subjective sentences. It also provides mechanisms for categorizing units of text and classifying text elements into predefined categories. You can use it to analyze text-based content including news feeds, emails, and postings on social media streams, such as Facebook, Twitter, and YouTube.

For more information, see Introduction to text analytics on the Pega 7 Platform.

Updates to the Data Flow rule

It is now possible to use report definitions as primary and secondary sources in the Data Flow rule. The data flows that are sourced by a report definition can be distributed on multiple nodes. When using a database table data set as the destination of the data flow, you need to select one of the save options for the data set (insert records or insert and update records).

Updates to the Event Strategy rule

When you design event strategies, you can use the Filter shape for basic arithmetic and text expressions. You can also specify start conditions for the tumbling and sliding windows.

Updates to the Predictive Model rule form

The Predictive Model rule form provides the XML schema preview for uploaded PMML models. You can use this preview to view the structure of a model and to correct errors before saving the rule. When the model contains errors, they are displayed in the Errors section at the bottom of the rule.

Support for custom pre- and post-JavaScript processing for offline flow actions

Developers of an offline-enabled mobile app can execute basic business logic before and after a flow action is rendered by adding their own JavaScript code into a custom user scripts bundle. Its functions must be called within a try/catch clause. The JavaScript code, to be executed before a flow action is rendered, is always called afterClientCache is called and before DisplayHarness is called.

Conditional online and offline map display

The way an Address Map control behaves in a offline-enabled mobile app has changed. When a mobile app is online, a live Google map is loaded as expected. If the mobile app goes offline, a predefined image of a map is loaded instead.

Troubleshooting Pega Mobile Client on the login screen

An offline mobile developer can now troubleshoot issues that are not related to incorrect credentials when signing in to the Pega Mobile Client app. On the app login screen, an alert box displays where the user can click a link to examine current log files to troubleshoot the issue. The contents of the displayed log file can be filtered.

For more information, see Troubleshooting Pega Mobile Client.

New Pega Mobile Client debugging options

The Mobile tab on the Application form contains two new options: a check box for enabling debugging in the Pega Mobile Client app, and a drop-down field for setting the log level to one of the following levels: Silent, Error, Warning, Info, or Debug.

For more information, see Mobile settings reference.

Ability to view a PDF file while offline

Users of offline-enabled mobile apps can now tap a button to view a PDF file, regardless of whether the user is online or offline. The associated button, link, or icon must have a Run Script action defined that calls the pega.ui.pdf.view() function with two parameters: applicationName and pdfName. The PDF file itself must be uploaded to a Rule-File-Binary rule.

For more information, see How to set up viewing of PDF file while offline.