Default filter settings for Pulse feed sources
Valid from Pega Version 8.3
Set default filters for Pulse messages, so that users see only relevant posts. Users can temporarily change these settings at run time to view messages from different feed sources, and restore the default settings by refreshing the page.
For more information, see Adding a feed source for the activity feed.
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.
Improved creation of When rules with the condition builder
Valid from Pega Version 8.3
Define conditions for When rules by using the condition builder view. You can create new or select existing values, and then group conditions with ANDs, ORs, or advanced logic. The condition builder does not support functions; the method for defining the conditions to use functions is the same as in the previous versions of Pega Platform™.
For more information, see Defining conditions with a condition builder, Defining conditions for a When rule.
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.