Report Browser removed from Designer Studio
Valid from Pega Version 7.1.9
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
Valid from Pega Version 7.1.9
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.
Verifying that a Pega 7 Platform instance is running
Valid from Pega Version 7.1.9
You can verify whether a Pega 7 Platform instance is up and running by entering this URL: http://<<hostName:port/contextName>>/PRRestService/monitor/pingservice/ping
The Pega 7 Platform Engine responds with HTTP Response Code 200 if the instance is available. The response contains JSON text in the format { "duration":"<time in milliseconds>" }. Any other response codes or timeout indicate that the instance is unavailable.
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.
Enabling historical compliance score data
Valid from Pega Version 7.1.9
Project stakeholders can now track the compliance score for an application over time to better understand and manage ongoing development adherence to Pega 7 Platform guardrails. The compliance score history can be displayed on a line graph on the Compliance Score tab of the Application Guardrails landing page. The data is collected daily and displayed in weekly increments, up to four weeks prior to the current date.
For more information, see Guardrails compliance score, Enabling compliance score history, and Compliance score trend reporting.
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.
Updated default system pulse processing settings
Valid from Pega Version 7.1.9
The default settings for system pulse processing have been updated in this release.
Upgrades to Pega 7.1.9 from a previous version of the Pega 7 Platform use database pulse by default. Database pulse synchronizes rule changes at a periodic interval across all nodes in a system.
New installations of Pega 7.1.9 use cluster-based pulse by default. Cluster-based pulse immediately updates rule changes across all nodes in a system after the changes are saved.
You can change the database pulse setting to the cluster-based pulse setting by updating the value attribute for initialization/pulse/transport to "cluster" in the prconfig.xml file or in the Dynamic System Settings. Changing from database pulse to cluster-based pulse requires a full cluster restart after the changes are made.
For more information, see Pega-RULES agents.
Application Sizing Wizard worksheet template now includes business impact
Valid from Pega Version 7.1.9
A column for business impact has been added to the project sizing template used by the Application Sizing Wizard. Project owners can now incorporate this assessment into their project sizing.