Published Release Notes

Cross-origin resource sharing (CORS) policies for APIs and REST services

You can now use cross-origin resource sharing (CORS) policies to control how external systems and websites (origins) are permitted to access resources such as APIs and services within your applications. For example, Pega^® Platform uses CORS policies to restrict which Pega Robotic client applications can connect to your Pega applications, and to limit which mobile apps can call Pega mobile services. Using CORS policies results in reduced cost and implementation times, while providing increased security when other systems or websites interact with your application.

For more information, see Creating a cross-origin resource sharing (CORS) policy and Mapping an endpoint to a cross-origin resource sharing (CORS) policy.

Pega Agile Studio integration

You can configure the new Agile Workbench tool to integrate with Pega^® Agile Studio so that bugs and user stories are synchronized between the two systems. In addition, you can improve traceability in your development environment by using the Current work feature to associate a user story or bug with development changes.

For more information, see Integrating Agile Workbench with Pega Agile Studio and Tracing development changes to work items.

Integrated Application Security Checklist helps you deploy a secure application

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.

Generate an XSD file for XML format output

You can now use Business Intelligence Exchange (BIX) to generate an XSD file for existing XML output when the Get all properties check box is selected on the Definition tab of the Extract rule form. You can now validate the XML output and generate DDL statements by using the generated XSD file. Some tags might not be included in the generated XSD file because of missing values in the XML output.

For more information, see Generating an XSD file for XML output.

Project sizing supports real-time feedback

You can now size a project based on the stories that you create in the Agile Workbench tool. By capturing feedback from your stakeholders in stories, you can improve the accuracy of your estimated timeline and costs in real time.
For more information about project sizing, see Sizing an application development project.

Improved usability for feature management

You can now manage your features more effectively by implementing the following changes in your application:

• Move features to different levels to change the structure of your feature hierarchy.
• Provide descriptions that are longer than 256 characters to improve the readability of features.
• Quickly remove irrelevant features without having to manage dependencies on built-on applications or previous application versions.
• Consolidate features into one application layer when you are ready to ship your application.

For more information about feature management, see Managing the features in your application.

Real-time statistics added to application overviews

You can now use the Application Overview landing page to get information about the number, type, and status of work items that are associated with your features. By referring to the statistics and progress bars that update as your team creates and resolves work items, you can track feature development in real time without interrupting your development team for status updates.

For more information, see Real-time statistics for feature development.

Encrypt sensitive case data by using a secure default Pega Platform cipher and AWS KMS keys

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

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.

Agile Workbench supports bulk actions

You can now create stories in bulk by importing a story template to Agile Workbench. By defining stories in bulk before you start development, you can size your project more quickly.

For more information, see Bulk actions in Agile Workbench.