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.
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 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.
Reconfiguration of the Adaptive Decision Manager service after upgrade to Pega 7.2.1
Valid from Pega Version 7.2.1
After you upgrade the Pega 7 Platform to version 7.2.1, you need to reconfigure the Adaptive Decision Manager service. Beginning with Pega 7.2.1, the Adaptive Decision Management (ADM) service is native to the Pega 7 Platform and is supported by the Decision data node infrastructure.
For more information, see Services landing page.
Reconfiguration of the Adaptive Decision Manager service after upgrade to Pega 7.2.2
Valid from Pega Version 7.2.2
After you upgrade the Pega 7 Platform to version 7.2.2 from a version prior to 7.2,1, you need to configure the Adaptive Decision Manager service. Beginning with Pega 7.2.1, the Adaptive Decision Management (ADM) service is native to the Pega 7 Platform and is supported by the Decision data node infrastructure.
For more information, see Services landing page.
Excessive service invocation count
Valid from Pega Version Pega Platform
Apply a hotfix to eliminate excessive service invocations. After upgrades, the service invocation count for Lucene search results might be up to four times greater than before the upgrade. The Pega 7 Platform moved from Lucene to Elasticsearch in Pega 7.1.7.
If any of the following situations apply to your installation, you must apply a hotfix:
- You installed any version prior to Pega 7.1.7 and you do not plan to upgrade at this time.
- You upgraded from any version prior to PRPC 6.3 to any version prior to Pega 7.1.7.
- You upgraded from 7.1.6 or earlier to Pega 7.1.7 or Pega 7.1.8 and you did not change your indexing to Elasticsearch.
The workaround depends on your version:
- For PRPC 6.3 SP1, apply HFix-27840 and HFix-28856.
- For other versions of the Pega 7 Platform, use My Support Portal to request the hotfixes for your system.
Beginning with Pega 7.1.9, the issue has been resolved.