Support for hotfix file verification
Valid from Pega Version 8.5
Pega Platform hotfix files are now digitally signed so that they can be verified and authenticated. If your Pega Platform™ instance allows outbound URL connections, hotfix files are verified automatically during installation. If your Pega Platform instance does not allow outbound URL connections, you can verify the files manually by using third-party tools. Alternatively, if your Pega Platform instance does not allow outbound URL connections and you do not use third-party tools to verify hotfix files, you can import a certificate revocation list (CRL) for Pega Platform to use when checking the files to see if they have been revoked.
For more information, see Verifying the authenticity of hotfix files.
Scenario tests now honor application stack settings
Valid from Pega Version 8.5
The application stack defined on the Application Quality Settings page of Dev Studio now serves as a foundation for creating, viewing, and running scenario tests.
Dev Studio will now:
- Display scenario tests based on the application stack settings on the Dev Studio landing page.
- Store scenario tests with the configured stack settings.
- Report metrics in the application quality dashboard with respect to the configured stack settings.
For more information, see Creating UI-based tests with scenario testing.
Run an application test suite from a CI/CD pipeline
Valid from Pega Version 8.5
Deployment Manager, as well as the existing REST service used to call scenario tests, now accepts a test suite ID when running scenario tests from an application pipeline. By using test suites, you can customize a set of select scenario tests to run as a group, instead of running all the scenario tests that are applied to a particular application.
Only the tests that belong to the suite are run as part of the task.
For more information, see Creating UI-based tests with scenario testing.
Access PegaUnit compliance metrics from a centralized location
Valid from Pega Version 8.5
PegaUnit compliance metrics and execution rate have been added to the PegaUnit metrics tile of the Application Quality dashboard. This dashboard provides a centralized location for all PegaUnit data for a specific application.
The dashboard also supports granular PegaUnit test information for each case type and data type, similar to the process currently available on the branch quality dashboard.
For more information, see Analyzing application quality metrics.
Run PegaUnit tests by using an API call
Valid from Pega Version 8.5
A new REST API is now available to create and run PegaUnit tests from an external continuous improvement (CI) tool. This synchronous method allows for the processing of large quantities of tests while reducing the possibility of time-out issues. This additional method of performing PegaUnit testing does not impact users who want to continue using their current testing workflow.
For more information about setting up your environment and making API calls with Deployment Manager, see the Documentation/readme-for-swagger.md file in the DeploymentManager04_08_0x.zip file, found in the Deployment Manager download package.
Merge application-level test reports by using the Pega API service
Valid from Pega Version 8.5
A new REST API is now available so that you can merge test coverage reports at the application level without having to perform this task manually. This service accepts the application IDs for the test coverage reports that you want to merge and generates a consolidated report in the target application provided.
For more information about setting up your environment and making API calls with Deployment Manager, see the Documentation/readme-for-swagger.md file in the DeploymentManager04_08_0x.zip file, found in the Deployment Manager download package.
Improvements to scenario testing for increased efficiency
Valid from Pega Version 8.5
Several enhancements have been made to scenario tests for increased test efficiency. See below for a list of these improvements.
- Scenario testing now supports multiple actions per run, and all events that are configured as part of a scenario test are now triggered sequentially. Previously, only the first event was triggered, and the system ignored the rest.
- If a scenario test encounters a JavaScript error at any point during the run, the system immediately stops the tests. Refer to the logs for a detailed description of the error.
- Actions can now be configured and recorded on custom components in the scenario testing tool.
For more information, see Creating UI-based tests with scenario testing.
Native synchronization indicators for offline-enabled mobile apps
Valid from Pega Version 8.5
Offline-enabled mobile apps now include a set of native synchronization indicators. Indicators keep users informed about the data synchronization status, for example, the Syncing indicator appears when an app regains network connectivity and starts receiving responses from the server. You can customize the indicators to better suit the look and feel of your mobile app. For more information, see Customizing synchronization indicators.
Upgrade impact
After upgrading Pega Platform™ to version 8.5, your app does not include native synchronization indicators until you update your application to use UI-Kit 15.
What steps are required to update the application to be compatible with this change?
Update the UI Kit in your application to version 15. For more information, see Updating the UI Kit in your application.
Uploading customer responses into adaptive models is no longer available
Valid from Pega Version 8.5
The option to train adaptive models by uploading a static list of historical interaction records has been deprecated in Pega Platform™ 8.5.
Upgrade impact
In versions of Pega Platform earlier than 8.5, it was possible to train an adaptive model by uploading historical data of customer interaction. After the upgrade to version 8.5, this option is no longer available.
What steps are required to update the application to be compatible with this change?
Use data from a report definition to train adaptive models. For more information, see Training adaptive models.
More flexibility for Date Time predictors in adaptive models
Valid from Pega Version 8.5
You can configure adaptive model predictors that indicate the amount of time that has elapsed since a particular event. In versions of Pega Platform™ earlier than 8.5, you could only specify the absolute date and time, for example, the date when a subscriber last visited one of your brick-and-mortar store locations. In Pega Platform 8.5, you can also indicate the amount of time that has passed, for example, the number of days since a subscriber purchased a new service plan.
For more information, see Adding a predictor to an adaptive model.