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.
Automatically process cases with Box
Valid from Pega Version 7.2.2
You can now use Box to store attachments during automated case processing without requiring user input at run time for authentication or authorization with Box. The authentication profile must be OAuth 2.0 with a grant type of authorization code. You can view which apps are connected, connect apps, and disconnect apps on the Connected apps landing page.
For more information, see Connected apps landing page.
Single sign-on (SSO) support for Box
Valid from Pega Version 7.2.2
You can now use SSO integration with Box so that users who have already been authenticated are not asked to reauthenticate when accessing Box from their Pega application. The Pega application and the Box application must use the same identity provider federation. This capability provides an integrated user experience and supports automated case processing of attachments.
For more information, see Authentication Profile data instances - Completing the OAuth 2.0 tab.
Send and receive queued messages securely with IBM MQ servers
Valid from Pega Version 7.2.2
You can now configure applications developed on the Pega 7 Platform for secure message queuing with IBM MQ servers by using the MQ server rule form. You secure the connection by specifying the cipher suites with encryption standards that meet your requirements and the SSL/TLS X.509 certificates that you use for authentication.
For more information, see Configure secure message queuing with IBM MQ servers.
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.
Improved responsiveness of tab layout groups
Valid from Pega Version 7.2.2
Tab layout groups are now more responsive when several tabs are displayed on a screen. The tabs are shown in a single row that you can scroll horizontally by pressing the left or right arrows. Additionally, you can switch to a tab directly by pressing the down arrow.
For more information, see Adding a Layout Group.
Semantic URLs in Pega Platform
Valid from Pega Version 8.5
URL addresses for Pega Platform™ applications and application resources now appear as clear, meaningful paths. This enhancement helps users understand the structure of the application that they are using, which makes navigation quicker and more intuitive.
Default views for cases and data objects
Valid from Pega Version 8.5
Pega Platform™ now generates default views for new case types and data objects. Because of this feature, your application now automatically creates a case summary and case details view for every new case type, and a list view for each data object. The default views automate a common recurring task, and improve productivity by reducing development effort.
Improved view authoring
Valid from Pega Version 8.5
Case authoring in Cosmos React UI now features updated view authoring tools. The redesigned view tab and overlay provide a more intuitive interface for creating views, applying design templates, and adding fields and controls. This enhanced work environment improves the user experience and reduces context switching, which contributes to a lower development effort.
For more information, see Editing views in a case type.