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.
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.
Data migration enhancements
Valid from Pega Version 8.3
Ensure a successful data migration by using a configuration template for setting up your environment before you migrate data into your application. From the new Migration settings landing page, configure dynamic system settings for migration and turn off database indexes and processes that might affect data migration performance. After you have finished migrating data, you can revert your system to its normal working state.
For more information, see Creating a migration configuration template.
Ability to import and export Intelligent Virtual Assistant or Email Bot training data
Valid from Pega Version 8.3
You can now copy Pega Intelligent Virtual Assistant™ (IVA) or Pega Email Bot™ training data between Pega Platform™ application environments by performing an export and import action. Importing and exporting training data between Pega Platform application environments results in greater accuracy of entity detection. Entities are detected by the system in a chat conversation, including attachments, to help respond to the user correctly, and consist of proper nouns that fall into a commonly understood category such as a person, organization, or a ZIP code. The ability to copy training data also makes it easier to maintain IVA or Email Bot, and build its artificial intelligence.
For more information, see Copying training data to another environment and Copy training data and model to another IVA or Email Bot environment.
Visual Data Model enhancements
Valid from Pega Version 8.3
View your application's full data model, see how its entities are related, edit and delete fields, and add fields to the model without exiting the Visual Data Model. In addition, you can now search the entire data model for fields and select a case or data type class to see its fields and relationships.
For more information, see Exploring the data model.
Use a JSON file to create a data type
Valid from Pega Version 8.3
You can now use a sample JSON response to create a data type in the Data Type wizard in Integration Designer. Using a sample JSON response reduces development time by providing the response schema when your REST endpoint is not available.
For more information, see Use a JSON file to create a data type.
Indicate download size in offline-enabled mobile apps for iOS
Valid from Pega Version 8.3
When you publish a client-based mobile app in the Apple App Store that needs to download additional resources before it starts, the app must indicate the size of the download and obtain user consent. To comply with this requirement, you can now build offline-enabled mobile apps that prompt the user before they perform the initial data synchronization. If the user chooses not to download data, the application closes.
For more information about disclosing the data size and how the data size is calculated, see Defining advanced offline configuration for an access group.
Support for decision tables in offline-enabled applications
Valid from Pega Version 8.3
You can now use decision tables to reduce the implementation time of your offline-enabled applications. By using decision tables you can further automate case processing and derive the logic from the data model. Decision tables can be referenced in a flow rule as a type of decision shape or called from the declare expression rule. No additional configuration is required to use decision tables in offline-enabled applications.
For more information, see Decision table support in offline mode.