Dynamic System Setting for selecting clipboard pages implementation
Valid from Pega Version 7.2.1
Create the dsm/clipboard/optimize Dynamic System Setting to select which clipboard pages to use for strategies and data flows in all contexts. Without this setting or with its value set to true, strategies and data flows work on DSM clipboard pages. When you set the value to false, strategies and data flows work on the conventional Pega 7 Platform clipboard pages. This Dynamic System Setting allows you to configure run strategies consistently and obtain consistent results.
For more information, see DSM clipboard pages implementation.
New service for generating OAuth 2.0 client credentials
Valid from Pega Version 7.3
Pega® Platform now includes the oauthclients service package that provides a REST service for generating OAuth 2.0 client credentials. By using the client registration service, you can dynamically register OAuth 2.0 clients. The new service is secured by an existing OAuth service. Access tokens that are issued by the existing OAuth service are accepted as initial access tokens by the new service.
For more information, see OAuth 2.0 Client Registration data instances.
Ability to run report definitions against an Elasticsearch index
Valid from Pega Version 7.4
To improve report generation performance, you can now run report definitions against Elasticsearch indexes instead of using SQL queries directly against the database. This feature is disabled by default and does not apply to reports that have features that are not supported by Elasticsearch. If a report query cannot be run against Elasticsearch indexes, Pega® Platform automatically uses an SQL query.
For information about enabling and using this feature, see Configuring a report definition to run against an Elasticsearch index.
Label changes for text analytic models
Valid from Pega Version 7.4
The classification analysis label has changed to topic detection and the entity extraction label has changed to text extraction. Also, the sentiment analysis, topic detection, and intent detection labels are now located under Text Categorization in the Analytics Center. These name changes reflect industry standards and provide a clearer distinction between different types of text analytics models in Pega® Platform.
For more information, see Text analytics models.
New assertions for data page unit test cases
Valid from Pega Version 7.2.1
You can now configure the following assertions for data page unit test cases:
- Result count assertions for page lists, page groups, value lists, and value groups
- Unordered list and ordered list assertions for page lists
The Pega 7 Platform now supports these assertions in addition to expected run-time assertions for the data page and property assertions for any property type.
For more information, see Data page unit test case assertions.
Mobile user interface updates
Valid from Pega Version 7.2
Several improvements have been made to the mobile-related user interface of the Pega 7 Platform. The content of the Mobile tab on the Application rule form has been redesigned. The Offline Configuration and Mobile Certificates landing pages are now available. The Signature Capture control has improved. Post-processing can now occur after the signature has been captured. You can auto-submit with the form submit. You can apply the signature to a page instead of applying it as an attachment to the case. The clear action completely removes the signature from the work object, keeping only the latest iteration of the signature. Touch interactions have been significantly improved. Response time is faster and there is better feedback on the touch action.
Information Mashup section for OAuth 2.0 provider authorization
Valid from Pega Version 7.2
You can now add an Information Mashup (pxInformationMashup) section to a layout, a region, another section, or a cell in a layout to delegate access to OAuth 2.0-protected resources. Configure the section with an OAuth 2.0 authentication profile, mashup section, and authorization section to connect to an external application at run time. For example, users can log on to Facebook from the Pega 7 Platform by using this section and access photographs in their Facebook account.
For more information, see Access protected API resources by using OAuth 2.0.
More efficient load management strategies for large data pages
Valid from Pega Version 7.2.2
The processing of large data pages on the Pega 7 Platform server during the packaging of offline apps is now faster and much more memory-efficient, especially in environments with many concurrent users. Server communication with the data source is now also optimized by reducing the number of data transfers to only what is needed. In addition, all types of refresh strategies are supported for large data pages.
For more information, see Tutorial: How to use large data pages to store large reference data in offline mobile apps.
Caching of common rules in offline mobile apps
Valid from Pega Version 7.2.2
To help start offline-enabled mobile apps more quickly from the time when the server was started, you can now cache common Pega 7 Platform rules, including node scope data pages. Optionally, you can also either cache all node scope data pages, with the exception of the selected ones, or cache only the node scope data pages that are explicitly specified. You set up the offline caching options for your custom mobile app in the Advanced tab of the Access Group rule form.
For more information, see the Offline Configuration section in Access Group form - Completing the Advanced tab.
Operator presence record tracks disconnected status of operators
Valid from Pega Version 7.3
The state attribute in the operator presence record now tracks the operator connection status of DISCONNECTED, in addition to tracking the operator connection status of ACTIVE, AWAY, or OFFLINE. Operators are disconnected if their browser crashes, if they close a browser session without logging out of the system, or if the network connection is down. The DISCONNECTED status helps prevent work from being routed to operators who are not online or not available.
When the operator restores the browser session or the network connection is restored, the Pega® Platform updates the operator connection status to ACTIVE.
For more information, see Tracking the online presence of operators.