New access control policy for encrypting properties
Valid from Pega Version 7.4
With attribute-based attribute control, you can now encrypt property values in the database, clipboard, logs, and search indexes for any property type. If no policy obfuscates an encrypted property, its value is visible in UI controls and reports.
For more information, see Creating an access control policy.
New privilege required to access the Search landing page
Valid from Pega Version 7.4
After upgrading to Pega® Platform 7.4, users who do not have the pxAccessSearchLP privilege cannot access the Search landing page. The pxAccessSearchLP privilege is automatically assigned to the SysAdm4 role. If you have other roles that require access to the Search landing page, you must add the pxAccessSearchLP privilege to those roles.
For more information about assigning privileges to roles, see User privilege authorization. (Link to: basics/v6portal/landingpages/accessmanager/customizeprivilegestab.htm)
Data Visualization controls are now available
Valid from Pega Version 7.4
Use a Data Visualization control when you need a highly configurable visualization beyond the standard pie, bar, and line charts. With a Data Visualization control, you can appropriately represent any type of data. You can add Data Visualization controls to sections or anywhere else a standard control can be used, such as dashboard widgets.
For more information, see Adding and configuring a Data Visualization control.
Configure role dependencies to grant access rights
Valid from Pega Version 7.4
You can configure role dependencies in a role to grant access rights, which are inherited from the role. Role dependencies are relationships between roles that mirror an organization hierarchy or a more complex relationship among groups of operators, roles, or functional areas. Use role dependencies to simplify role configuration, minimize the number of roles needed by an access group, and minimize the number of privileges that you have to manually define for roles in your application.
For more information, see Access Role rules, Access Role form – Using the Role tab.
Support for controlling binary file upload in Pega Mobile Client
Valid from Pega Version 7.4
The Client Store API of Pega® Mobile Client has been modified so that you can suspend and resume the process of uploading binary files to the server. You can also check the state of the file uploading process. As a result, custom mobile app users can process their work items without having to wait for the synchronization process to finish.
For more information, see Pega Mobile Client API methods for controlling binary data upload and Client Store API.
VTable dispatch mechanism for HTML control execution improves performance
Valid from Pega Version 7.4
Pega® Platform now uses an optimized VTable dispatch mechanism to manage rule execution for the Text Input and Formatted Text Input controls. This change improves performance by eliminating the dependency between stream rules and HTML controls during rule assembly. Disabling this feature will have a negative effect on performance and is not recommended. However, you can disable this feature by adding the following configuration parameter:
Name: assembly/section/control/vtable
Value: false
Improve application quality by using test coverage metrics
Valid from Pega Version 7.4
You can now generate a test coverage report for your application. By using report metrics that show the number of rules covered and not covered by tests, developers can identify which areas of the application need more test coverage.
For more information, see Rules Coverage landing page.
Decisioning services now use default node classification
Valid from Pega Version 7.4
Decisioning services have been integrated with default node classification on Pega® Platform to provide a unified way of creating and initializing services. As a result of the integration, the Data Flow service has been divided into Batch and Real Time services to better handle different types of data flow runs. You can now specify separate subsets of Data Flow nodes for batch data flow runs and real-time data flow runs to divide the workload between these two subsets.
For more information, see Node classification, Data Flows landing page, and Services landing page.
Aggregate data in interaction history summaries
Valid from Pega Version 7.4
You can now group, aggregate, and filter interaction history data in a single strategy component. By using interaction history summaries, you can create refined data sets that simplify strategy frameworks and accelerate decision-making. Aggregated data sets are easier to process, manage, and troubleshoot.
For more information, see Data Sources landing page
Support for additional health metrics on the Application Quality landing page
Valid from Pega Version 7.4
On the Application Quality landing page, you can monitor the health of your current application to identify areas that need improvement before deployment. The landing page provides application metrics such as the number of executable rules, the guardrail score, the number of guardrail warnings, the test coverage percentage, and the pass rate of PegaUnit tests. From this landing page, you can also view data for the entire application, for each of its cases, and for rules that are not part of any case type.
For more information, see Application Quality landing page.