The Scratch Pad tool is no longer available
Valid from Pega Version 7.3.1
The Scratch Pad tool is no longer available. To add properties to a report from an end user portal, use the Data Explorer. The Data Explorer provides an efficient way to find a property or calculation to include as a column in a report.
For more information, see Data Explorer.
Integrated Application Security Checklist helps you deploy a secure application
Valid from Pega Version 7.3.1
Pega® Platform now provides an Application Security Checklist that you can refer to when you prepare your application for deployment. By completing the recommended tasks in this checklist, you can track your progress, access instructional information for tasks, and verify that your configurations are secure.
For more information, see Preparing your application for secure deployment, Compliance Score tab, Designer Studio — Home page.
Encrypt sensitive case data by using a secure default Pega Platform cipher and AWS KMS keys
Valid from Pega Version 7.3.1
You can encrypt sensitive data within your application without having to write custom cipher classes. You can configure encryption on the Data Encryption landing page by using your own keys managed in your private Amazon Web Services Key Management Service (AWS KMS) instance. Pega® Platform encryption uses keys that are stored in AWS KMS to support both time-based and on-demand key rotation. Technical issues can arise in some cases, for example, if a key is deleted from AWS KMS.
For more information, see Potential problems with keystores when using AWS KMS, Configuring a Platform cipher, Types of ciphers.
REST services support password credentials and JWT Bearer grant types
Valid from Pega Version 7.3.1
Pega® Platform REST services now support password credentials and the JWT (JSON Web Token) Bearer grant type when you enable OAuth 2.0-based authentication. By using password credentials, you can quickly migrate clients from direct authentication schemes, provide additional flexibility when other grants are not available, and integrate your application with REST services in other applications. You can add compatibility with modern JWT-based cloud security IDPs by using the JWT Bearer grant type.
For more information, see About OAuth 2.0 Provider data instances, OAuth 2.0 Client Registration data instances - Completing the Client Information tab, Creating an Identity Mapping data instance.
Custom scaling on x-axis for bubble charts
Valid from Pega Version 7.3.1
Bubble charts now support custom scaling for the x-axis as well as the y-axis. For example, you can now configure a fixed range for the x-axis.
For information about including a chart in a report, see Adding or editing charts from the Report Definition rule form.
Enable users to save charts as .png files
Valid from Pega Version 7.3.1
You can now enable users to save a report chart as a .png file. On the Chart tab of the Report Definition rule form, click General settings and select the Export chart to image check box. When you select this option, users are provided with the Save as image option, which they can use to save an image of the chart to include in a Word document or email.
For information about including a chart in a report, see Adding or editing charts from the Report Definition rule form.
Enhancements to exporting reports to Excel
Valid from Pega Version 7.3.1
When you export report results to Microsoft Excel, the process now creates a Data sheet and an Info sheet in the Excel file. By default, the Info sheet contains the report title, filters used to generate the report, the date when the report was generated, and the number of results returned.
If you want the report title and filters to display in the first sheet instead of the Info sheet, you can disable the default functionality. For more information, see Disabling the creation of an Info sheet in Excel output.
View status of custom search indexes
Valid from Pega Version 8.1
Custom search indexes are special purpose indexes that are created and managed outside of Pega Platform™. You can view the status of custom search indexes on the Search landing page to see whether they are complete. This information is useful for troubleshooting and can help you determine whether to rebuild the index.
For more information, see Checking search index status.
Support for OAuth 2.0 authorization code grant type
Valid from Pega Version 8.1
Pega Platform™ now supports the OAuth 2.0 authorization code grant type, which allows Pega Platform to act as an OAuth 2.0 access token provider for native applications on mobile and other devices. By using the authorization code grant type for mobile clients, you no longer need to implement a variety of standards for various authentication providers. The authorization code grant type also supports the Proof Key for Code Exchange standard (PKCE) for securing public clients.
For more information, see Creating and configuring an OAuth 2.0 client registration.
Use client-based access control to support EU GDPR requirements
Valid from Pega Version 8.1
You can use client-based access control (CBAC) to satisfy the data privacy requirements of the European Union General Data Protection Regulation (GDPR) and similar regulations. By using client-based access control, you can identify the personal data of clients and automatically process requests to view, update, or remove the data in a secure manner. You can also enforce restrictions on the use of this data in application functions.
For more information, see Client-based access control.