Page assertions are supported for PegaUnit test cases
Valid from Pega Version 7.2.2
You can now create page assertions for PegaUnit test cases. Because data transforms and activities can create or remove pages, you can configure page assertions to determine whether a page exists after you run PegaUnit test cases.
For more information, see Configuring page assertions.
New Automated Testing landing page
Valid from Pega Version 7.2.2
The new Automated Testing landing page displays all the PegaUnit test cases in your application. You can use it to quickly access, run, and view results of tests. In addition, if you have the AutomatedTesting privilege enabled, you can switch to the Automated Unit Testing landing page to access rules that are supported by both PegaUnit testing and Automated Unit Testing, such as activities.
For more information, refer to Automated Testing landing page.
Run advanced agents on only one node in a cluster
Valid from Pega Version 7.2.2
You can now configure an advanced agent to run on only one node in a cluster at a specified time. In addition, you can specify the time interval within which an advanced agent runs on only one node in the cluster, which avoids having two advanced agents starting to run on the same node at the same time.
For more information, see Improved control for running advanced agents and Agents rules – Completing the Schedule tab.
Ability to test SELECT statements
Valid from Pega Version 7.2.2
When developing and debugging applications, you can test SELECT statements from the Query Runner landing page. You can run queries against non-BLOB columns in your database and view the results on the landing page or export the results to an Excel spreadsheet or PDF file. This functionality is available for Pega Cloud customers who use a Postgres database or for customers using an Oracle database on-premises or on the cloud.
To use this landing page, you must have the PegaRULES:DatabaseAdministrator role or the pxDBSelectQuery privilege in Data- and Rule- in your access group. You access the landing page by clicking .
For more information, see Query Runner landing page for testing SELECT statements.
Authenticate REST data sources by using OAuth 2.0
Valid from Pega Version 7.2.2
You can now authenticate the data sources that are created from your REST integration by configuring OAuth 2.0 authentication in the New REST Integration wizard. You can specify or create an OAuth 2.0 authentication profile in the wizard by using the client credentials or authorization code grant type.
For more information, see OAuth 2.0 in REST integration.
Elasticsearch 2.4.0 upgrade
Valid from Pega Version 7.2.2
The Pega 7 Platform has been updated to use Elasticsearch 2.4.0. You do not have to reindex immediately. You can reindex at your convenience by using the FullTextindexer utility, which provides a smoother transition to the next Elasticsearch library upgrade.
Rolling upgrades are not supported. Instead, after the upgrade has been completed, shut down all the nodes in the cluster, and then restart them beginning with the indexing nodes. For more information, see the Pega 7 Platform Upgrade Guide on the Deployment Guides landing page.
Robotic Desktop Automation (RDA) support for Pega 7 applications
Valid from Pega Version 7.2.2
You can use Robotic Desktop Automation (RDA) to integrate and unify processes that run on a user's desktop to streamline work and free your staff to focus on higher-value, customer-oriented tasks. You can use automations to retrieve information from applications that run on the desktop and send them to your Pega 7 application, and you can also use automations to send information from your application to applications that run on the desktop.
In an example Call Center application, you can use an automation to retrieve information from a legacy application running on a customer service representative's (CSR) desktop and display it in your application. You can also send information that users enter in your application (for example, an address change) to an automation to update the legacy application.
For more information, see:
New hashing algorithm for Password property types
Valid from Pega Version 7.2.2
To provide extra protection against brute-force attacks, a new hashing algorithm has been added to the Pega 7 Platform. Bcrypt is used as a default hashing algorithm for Password property types. The bcrypt key setup algorithm takes a long time to process. This means that potential attackers would have to spend a substantial amount of time testing every possible key.
For more information, see Using the bcrypt hashing algorithm for Password property types.
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.
Discovery features for access control policies
Valid from Pega Version 7.2.2
Access control policies now support discovery features that allow end users to view limited, customizable information about class instances that fail Read policies but satisfy Discover policies. Two types of Discovery gadgets are provided, and when discovery features are enabled, a Discovery gadget is included in the Report Viewer and in search results. Developers can customize these gadgets and include them in other parts of an application user interface.
For more information, see Discovery features for access control policies.