Attribute-based access control model
Valid from Pega Version 7.2.1
Attribute-based access control (ABAC) is a security authorization model in which access rights are determined through the use of policies and attributes. A policy decision engine in ABAC evaluates digital policies against available data (attributes) to permit or deny access to the requested resource. For example, you can now determine access rights to cases by examining security attribute values assigned to the user and the case.
For more information, see Attribute-based access control.
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.
Access work items directly after login
Valid from Pega Version 7.2.1
You can now directly access work items that you receive as email notifications or URLs. The Pega 7 Platform opens the work item after successful user authentication instead of redirecting you to the portal. For a valid user, the type of authentication or number of failed login attempts does not affect this direct access.
For systems that use basic or secure basic authentication, administrators can disable the redirect URL by setting the authentication/basicschemes/redirectToLoginScreen switch to false.
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
Open access to quiesced servers when using immediate drain
Valid from Pega Version 7.2.1
When using the immediate drain method to perform quiesce on a node, any operator can now access a quiesced server for root cause analysis or remediation, regardless of their user role or privileges. For quiesced server access when using the slow drain method, you must still include either the PegaRULES:HighAvailabilityAdministrator or PegaRULES:HighAvailabilityQuiesceInvestigator user role in a user's access group. Administrators using the slow drain method without either of these user roles are exiled from the quiesced node and are redirected to an active node.
For more information, see Immediate drain available for quiesce when using high availability.
Easy access to proposition-related rules when creating change requests in revision management
Valid from Pega Version 7.2.1
When selecting propositions for change requests in Decision Strategy Manager, you can view the proposition filter, strategy, and when rules that are associated with the decision data the selected propositions belong to. In addition, you can include those rules in change requests. To view and add any associated rules to a change request, the rules must be part of the application overlay. With the ability to view and select all proposition-related data, you can consistently revise not only propositions themselves but also all associated rules.
For more information, see Proposition-centric revision management functionality.