Swipe actions in repeating dynamic layouts in a mobile app
Valid from Pega Version 8.3
Lists that are based on repeating dynamic layouts now support swipe actions. The menu of available actions, such as Edit or Delete, does not obscure the view and is displayed only when a mobile app user swipes a row. Users benefit from easier navigation and they can do smaller tasks quickly, without leaving the main screen.
For more information, see Configuring swipe actions for a mobile app.
Web mashups preview
Valid from Pega Version 8.3
App Studio now has a preview mode that shows how an integrated Pega application is displayed on a chosen website. You can try different host sites, as well as window sizing types and skins, to find the best presentation options.
For more information, see Creating a mashup demo.
Numbered accordion for layout groups
Valid from Pega Version 8.3
Layout groups and dynamic layout groups with the accordion layout now support automatic numbering of collapsible headers. You can now build better user forms, as the numbers show the steps that users need to follow to fill out a form so that they know the process stage at every moment. Automatic numbering accommodates when conditions that are used in accordion sections.
For more information, see Creating a layout group.
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.
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 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.
Automatically generate OpenAPI Specification documentation for application REST APIs
Valid from Pega Version 8.3
You can now access a clear, standard view of all the REST APIs in your application by using autogenerated OpenAPI Specification (OAS) documentation. In App Studio, you can view the OAS documentation generated for application-specific REST APIs by using the new Application tab in the API channel. Additionally, service package rules now include an OpenAPI tab where you can view the automatically generated OAS documentation for all the REST services included in the service package. With these enhancements, you can easily find, visualize, and test the REST APIs in your application.
For more information, see Generating OpenAPI Specification documentation for application-specific REST APIs.
Define a default reporting database
Valid from Pega Version 8.3
You can now easily define a reporting database for all classes that are assigned to a primary database. You can also assign this reporting database as the default reporting database. This provides support for reporting against Amazon Aurora read replicas. AWS Aurora increases the performance and stability of your database management system.
For more information about reporting, see Report Definition data access tab.