A new transition effect for actions in custom mobile apps
Valid from Pega Version 7.2.2
Custom mobile apps that are developed on the Pega 7 Platform can include a new transition effect that animates your navigation in cases that use flows. This feature adds to the look-and-feel experience of the custom mobile app.
You can also add the pega.mobile.transitions.GO_HOME transition effect to actions that do not support built-in effects by using the Run Script action and calling the pega.desktop.setNativeTransition() JavaScript method.
For more information, see Transition effects on actions.
Pega Client for Windows
Valid from Pega Version 7.2.2
Pega Client for Windows is a stand-alone application that serves as a container for Pega 7 Platform applications. The target for this product is Windows 10 laptops and tablet devices. It communicates directly with the Pega 7 Platform server to support online and offline-enabled applications. Pega Client for Windows works on 32-bit (x86) and 64-bit (x64) Windows devices.
For more information, see Features and functions of the Pega Client for Windows.
Automatic creation of large data pages from Report Definitions
Valid from Pega Version 7.2.2
Offline-enabled mobile apps now use Report Definitions to automate filtering logic for controls that are based on large data pages. You no longer have to use custom JavaScript functions (custom populators) to create large data pages.
For more information, see How to use large data pages to store large reference data in offline mobile apps.
Remote device log retrieval
Valid from Pega Version 7.2.2
You can access device logs without end-user involvement by using the device log retrieval functionality. The Pega 7 Platform downloads logs from a specific user's device during data synchronization events. You can use these logs to troubleshoot and support offline-enabled custom mobile apps.
For more information, see Device logs.
SAML 2.0 single sign-on authentication in multitenant environments
Valid from Pega Version 7.2.2
Multitenant application environments can now use SAML 2.0 for single sign-on (SSO) and single logout (SLO). Application users can access any authorized SSO multitenant applications without logging in to each application individually. SAML simplifies the login and logout process for users, mitigates security risks, and reduces the implementation costs that are associated with identity management.
For more information about configuring SAML 2.0 for single sign-on, see Web single sign-on (SSO) with SAML 2.0.
New PegaRULES:PegaAPISysAdmin role
Valid from Pega Version 7.2.2
The role PegaRULES:PegaAPISysAdmin has been added to the Pega 7 Platform. This required role gives system administrators access to the Pega API REST User Services and is not required for other services.
For more information, see Securing the Pega API.
Issue with the Sandbox directive on the Content Security Policy rule form has been fixed
Valid from Pega Version 7.2.2
An issue that related to the Sandbox directive not being applied, even after a value in the Content Security Policy rule form was selected, has been fixed. As a result, restrictions that are applied based on the settings in the Sandbox directive are now more closely aligned with the World Wide Web Consortium (W3C) specification than in previous releases. You should test your Content Security Policy to ensure that this change does not cause unexpected behavior in your application, such as making the security policy too restrictive.
Improved capability to attach content in offline-enabled applications
Valid from Pega Version 7.3
The feature for attaching content in applications while in offline mode has been enhanced. A list of attached content is displayed in the application while in offline mode. You can view or delete attachments if the application has not yet been synchronized with the server. You also can change the maximum size of a file that you can attach while working in offline mode. This option gives you the flexibility to select the right size of attachment for a specific application for performance, memory limitation, or security reasons.
For more information, see Attach content support in offline mode.
Monitor standard and custom security events
Valid from Pega Version 7.3
From the new Security Event Configuration landing page, you can select the standard and custom security events that you want the Pega 7 Platform to log automatically for every user session. The security events are grouped into the following types:
- Authentication
- Data access
- Security administration
- Custom
The API logCustomEvent() is provided so that you can create custom security events that are specific to your applications and that can be monitored by the Pega 7 Platform. For more information, see Security Event Configuration.
SAML configuration supports global resource settings
Valid from Pega Version 7.3
In the SAML Authentication Service form, you can now use global resource settings, which allow greater flexibility for values that change compared to using fixed text values. Apply global resource settings, which are dynamic values, in the Identity Provider (IdP) information section and the Service Provider (SP) settings section of the form.
For more information, see Authentication Service form - Completing the SAML 2.0 tab.