The use of MBeans for cluster management has been deprecated, although MBeans will continue to function for legacy deployments. The recommended best practice for automating system management is to use the Pega API. For more information, see Pega API.
Valid from Pega Version 8.4
Pega Platform™ now provides you with an option to edit the list of features in your application stack. Now you can define the order of the features to generate application documentation that lists the features by their priorities instead of the time of creation. For example, you can reorder the features when you want to communicate to your stakeholders which elements are top priorities.
Pega Platform™ now supports the enhanced Wait shape that configures the case to wait for the resolution of all child cases instead of only the child cases of a specific type. When you set up the Wait shape to stop a case until it reaches a certain status, you can decide whether the shape considers statuses from a whole case life cycle, or only the statuses after the wait begins. The enhanced Wait shape provides you with greater control over resolution of your cases.
Data pages that are sourced from report definitions now support server-side paging. This functionality optimizes the performance and memory of data pages, making them more efficient at retrieving large lists of data. In addition to getting page indicators at the top of a grid, you can sort and filter columns in a grid in conjunction with paging. If you want the system to use server-side pagination, you can also enable pagination from the Data page rule form.
You can now access external APIs by using the new OAuth 2.0 JSON Web Token (JWT) Bearer grant type, in an OAuth 2.0 authentication profile. To use the JWT Bearer grant type as a client assertion, source the JWT from an active SSO session, a token profile, or a property reference. You can use JWTs that you obtain during an OpenID Connect SSO in connectors, to achieve user impersonation flows, such as the On-Behalf-Of (OBO) flow. The OAuth 2.0 type authentication profile now also supports authentication of client applications by using Private Key JWTs.
Instances of the OAuth 2.0 provider are now deprecated. As a best practice, use the new, unified authentication profile configuration instead.
After an upgrade to Pega Platform 8.4 and later, Authentication Profiles can take advantage of the new JWT based OAuth 2.0 grant type and client authentication features. To take advantage of this and other new security features, you must update any existing Authentication Profiles formats must to use those in Pega Platform 8.4 and later.
What steps are required to update the application to be compatible with this change?
Since these features are available only for profiles created in Pega Platform 8.4 and later, clients must open and then save existing 'Authentication Profile' instances to ensure that the configuration is compatible with the latest authentication formats.
Valid from Pega Version 8.4
Email integration with Microsoft Office 365 now supports Microsoft Graph. By using Microsoft Graph, you can process inbound email more securely and avoid using less secure protocols, such as IMAP and POP3.
Create restore points to save the state of all rules and data in your system at a significant point in time, for example, before you import an application. Roll back to that restore point to return the system to that state. Now, you can filter which rule and data instances are returned to their previous state:
System: Roll back every rule and data instance that has a history record.
User: Roll back rule and data instances modified by a specific user. If any rule was changed by more than one user, you will see an error message and must use the system rollback.
Application: Roll back rule and data instances in a specific application.
Make the most of your custom Amazon SageMaker models in Pega Platform™ by connecting to the models in Prediction Studio. You can then run the Amazon SageMaker models as part of your decision strategies.