Update access groups from the command line
Valid from Pega Version 7.2.2
Remotely update access groups by using the prpcServiceUtils tool. This feature is useful in automated deployment scenarios when you want to provide access to a new application version.
For more information, see Updating access groups from the command line.
Robotic Process Automation (RPA) support for Pega 7 applications
Valid from Pega Version 7.2.2
You can now use Robotic Process Automation (RPA) to automate repetitive and unattended back-office activities directly from your Pega 7 application. By using RPA with your application, you can batch process large volumes of cases faster and with fewer errors compared with manual case processing. You configure the automations in Pega Robotics Automation Studio.
For example, when an automobile insurance claim is submitted, an automation can analyze the submitted information, look up and verify policy holder information, and update web and desktop applications with case information.
For more information, see:
Extended support for Dutch, Italian, and Portuguese in text analytics
Valid from Pega Version 7.2.2
The number of supported languages in the sentiment analysis feature of the Pega 7 Platform has been increased through the addition of sentiment lexicons for Dutch, Italian, and Portuguese in Text Analyzer rules. By using these lexicons, you can now determine the emotional tone of text samples that are written in these languages.
For more information, see Text Analyzer.
Free Text Model rule type name changed to Text Analyzer
Valid from Pega Version 7.2.2
The name of the Free Text Model rule type has been changed to Text Analyzer. When you upgrade to Pega 7.2.2, the rule type name of all Free Text Model rules in your application will change automatically to Text Analyzer.
For more information, see Text Analyzer.
Trace agents from the Agent Management landing page
Valid from Pega Version 7.2.2
You can now trace an agent on any node in the cluster from the Agent Management landing page without logging in to the individual nodes. From this landing page, you also specify when to trace an agent.
For more information, see Tracing agents.
New graphical layout and shapes on the Data Flow form
Valid from Pega Version 7.2.2
The Data Flow form has an enhanced layout that improves interaction with objects on the canvas and provides better readability of flow shapes. The enhancements also include the addition of Branch and Data Transform shapes, and the Convert shape, which supports page unpacking. With these enhancements, you can build data flows more efficiently and capture business requirements more effectively.
For more information, see Improvements to the Data Flow rule form and New shapes on the Data Flow form.
Terminate sessions for operators from outside the Pega 7 Platform
Valid from Pega Version 7.2.2
The newly added Users REST API allows an authorized administrator to terminate sessions for one or more operator IDs from outside the Pega® 7 Platform. A typical use case for this API is to terminate a user’s session when the user's security credentials, which are stored externally, are known to have changed.
Access the Pega API by clicking .
Improved scrollable layouts in a new harness
Valid from Pega Version 7.2.2
By default, you can now create a new harness with a screen layout instead of as a container with a cell structure. This change ensures that you can create an application layout more efficiently; for example, you can specify a scroll area exactly the way you want in a desktop application or a mobile app. You can arrange the header, footer, and main area content at the new harness level by using sections. For example, you can specify headers and footers to be fixed or to scroll with the page. New layout options are configurable in the skin. Different layout selections are available when you use the harness as an app view, a main area, inner harness, or a page view.
For more information, see Configuring a screen layout.
Client page load statistic enhancements
Valid from Pega Version 7.2.2
The client page load statistic is the total elapsed time from when the user clicks to when the screen has finished rendering, including network time and time spent in the browser. This statistic gives you visibility into system performance, allowing you to address performance issues in a timely manner. The client page load statistic is now available for usage reporting through the Log-Usage class and in the System Management Application (SMA). In addition, a new alert, PEGA0069, is generated when the page load duration is greater than the threshold. The threshold is set by using the following prconfig.xml file setting:
<env name="alerts/browser/clientPageLoadTimeThreshold/warnMS" value="<milliseconds>" />
The default is 4000 milliseconds.
For more information, see PEGA0069 alert - Client page load time has exceed the alert threshold.
Cluster-wide tracing for service rule
Valid from Pega Version 7.2.2
RuleWatch Tracing of Service Rules has been enhanced to support cluster-wide tracing. Cluster-wide tracing makes it easier for you to troubleshoot services in clustered configurations where a load balancer dynamically assigns service requests to nodes in the cluster. This functionality is especially useful for debugging mobile applications, REST Web Services, and other stateless service executions. When tracing across the cluster, the trace feature captures only one trace at a time, which might result in some concurrent service executions not being traced. All other concurrent service executions in the cluster continue unimpeded. When the trace in progress is completed, the next new service execution in the cluster is traced. For example, you might see traces for invocation one on node A, invocation two on node C, and invocation four on node B. This selective tracing approach ensures that tracing with a breakpoint will not stop all service executions across the cluster. The trace/cluster/ServiceRuleWatchmaxProductionLevel Dynamic System Setting has also been added, which allows you to selectively disable tracing based on production level to eliminate performance issues related to tracing in production systems.
As a result of this enhancement, only one user can trace a service rule at any given time. An error message is displayed if you try to trace a service rule that is being traced by another user.
For more information, see Cluster-wide tracing of service rules.