Facilitated application development with saving changes in branches in App Studio
Valid from Pega Version 8.3
For improved development of your application, you can now define branches in which you save changes that you make to your application in App Studio. Create features in branches so that you can review and merge them without affecting other features in the application. You can quickly identify and review any changes to rules because you know in which application layer they were saved.
For more information, see Setting branch preferences in Dev Studio, Setting branch preferences in App Studio.
Token credentials authentication service
Valid from Pega Version 8.3
You can create a new type of authentication service for token credentials authentication, which is useful for offline mobile applications. With token credentials authentication, users need to enter their credentials only once in a session. Subsequent access to the server is authenticated with a token. The token can be generated by the Pega Platform™ authorization layer (OAuth 2.0) or issued by an external identity provider.
For more information, see Configuring a token credentials authentication service.
Platform truststore for validating certificates
Valid from Pega Version 8.3
Pega Platform™ now includes a platform truststore, to which you can import X.509 certificates that are common across platform applications. When a certificate needs to be validated, Pega Platform looks for the certificate at the connector level, then in the platform truststore, and finally in the application server (JVM) truststore. You can add, update, and delete certificates in the platform truststore without having to restart the server, which is useful when TLS certificates are changed for reasons such as key rotation.
For more information, see Importing an X.509 certificate.
Stream-based alternative for interaction history
Valid from Pega Version 8.3
Accelerate the processing of high-volume interaction history data by incorporating a stream-based interaction history into your application. A stream-based interaction history processes large volumes of data more quickly than a traditional relational database interaction history so that you can react to your customers' needs in real time.
For more information, see Process high-volume interactions more efficiently and Aggregates-only mode for a stream-based interaction history.
Aggregates-only mode for a stream-based interaction history
Valid from Pega Version 8.3
Activate the aggregates-only mode to efficiently transition your application from a relational database interaction history to a stream-based interaction history. By transitioning from a traditional relational database interaction history to a stream-based interaction history, you enable your application to process large volumes of data more quickly so that you can react to your customers' needs in real time.
For more information, see Transitioning to a stream-based interaction history.
Support for controlling simulations in Integration Designer
Valid from Pega Version 8.3
Integration Designer now supports toggling an existing simulation for a data source on and off, and supports creating a simulation when a data source does not have a simulation configured. By simulating a data source, you can continue developing an application when your integration is not available, and test an application independently from the integration.
For more information, see Managing data and integrations with the Integration Designer.
Support for additional key management services
Valid from Pega Version 8.3
By supporting additional key management services, Pega Platform™ offers you increased flexibility when defining keys that are used for encryption of application and internal system data. You can now create keystores that reference keys from key management services such as Microsoft Azure Key Vault, HashiCorp Vault, and Google Cloud KMS, in addition to Amazon KMS. You can also create a keystore that references other key management services through the use of a data page.
For more information, see Configuring a Microsoft Azure Key Vault keystore, Configuring a HashiCorp Vault keystore, and Configuring a Google Cloud KMS keystore.
Ensure event strategy reliability through unit tests
Valid from Pega Version 8.3
You can now automate event strategy testing and increase the reliability of the event strategy configuration through unit tests. Avoid errors and ensure that the strategy delivers the expected results by configuring assertions on property values, aggregates, and result counts.
For more information, see Increased event strategy reliability through unit testing.