Data flow destination is resolved at assembly time
Valid from Pega Version 7.1.8
Data flow execution always uses the design-time destination data sets or destination data flows, regardless of the input records at run time.
Example:
You create a data flow and set the destination to a specific data set. In the data flow, you use a strategy that produces some results. Regardless of these results, the execution of your data flow always uses the destination data set that you specified when you designed the data flow.
The same applies when you set the destination to a data flow.
Text analytics on the Pega 7 Platform
Valid from Pega Version 7.1.9
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
Valid from Pega Version 7.1.9
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
Valid from Pega Version 7.1.9
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
Valid from Pega Version 7.1.9
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.
Updates to the Strategy rule
Valid from Pega Version 7.1.9
The Strategy tab of the Strategy rule form contains a new Test runs panel from which you can run simulations and test strategies for single and multiple customers. When you test strategies for multiple customers, you can identify the most popular propositions offered to the customers, check the overall strategy performance, and examine the performance of the individual components.
Pega 7 Express is available on-premises
Valid from Pega Version 7.1.9
You can now experience Pega 7 Express by switching your enterprise application from Designer Studio to express mode. By default, users with access to the Developer portal can switch between these two development environments. You can also create an express application to work in express mode exclusively.
Trial versions of Pega 7 Express continue to be available on the cloud. To view the documentation for both the cloud and on-premises environments, see Getting started with Pega 7 Express.
Access to Pega 7 Express from within Designer Studio is not supported on mobile devices.
Context-specific documentation is not available in express mode
Valid from Pega Version 7.1.9
Help topics that are opened from express mode display content that is specific to Designer Studio.
If your system is dedicated to applications that are developed in express mode exclusively, and you do not need Designer Studio help topics, you can set the Online Help URL field on the System Settings landing page to: https://pdn.pega.com/sites/default/files/help_p7e/procomhelpmain.htm. Alternatively, you can view the contextual help system for Pega 7 Express in a separate browser tab.
Design-time limitations in express mode
Valid from Pega Version 7.1.9
Some limitations apply when you develop an enterprise application in express mode. At design time, some features are disabled or have limited options when you configure them in Designer Studio and switch to express mode. The use of these features does not restrict the run-time behavior of your application; however, you cannot change the configuration of these features unless you switch from express mode to Designer Studio.
For more information about each limitation and the recommended action to take, see the following information:
- Pega 7.2.2 Design-time limitations in express mode
- Pega 7.2.1 Design-time limitations in express mode
- Pega 7.2 Design-time limitations in express mode
- Pega 7.1.9 Design-time limitations in express mode
New types of data sets
Valid from Pega Version 7.1.9
There are three new types of data sets:
- Facebook - Required for connecting with the Facebook API
- Twitter - Required for connecting with the Twitter API
- YouTube - Required for connecting with the YouTube Data API
Use these data sets when you create instances of the Free Text Model rule and you want to analyze the text-based content on social media streams such as Facebook, Twitter, or YouTube.