Published Release Notes

Merge application-level test reports by using the Pega API service

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

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. 

WSDL generation error prevents invocation of SOAP services

Status

A Known Issue was introduced in the 8.4.2 Pega Platform patch release, which impacts both upgrades and new installations of that version.

Description

Due to changes introduced in the SOAP functionality for the case-mismatch error in SR-D98509/INC-119725, the WSDL is being generated for SOAP services with an incorrectly-capitalized element, which prevents the service from being invoked.  The element should be “name” instead of “Name”.

Workaround

Clients must perform the following workaround after they define a new SOAP connector in Pega Platform:

1. To download the WSDL from Pega Platform:
   1. After using the SOAP Wizard (Dev Studio > Configure > Integration > Services > Service Wizard) the WSDL URL is shown at the bottom right of the Dev Studio screen.
   2. Click the URL to display the XML.
   3. Save the WSDL file to your local system.
2. In the text editor of your choice, modify "Name" to "name" in every <element “name” = … > tag in the WDSL.
3. Save your changes to the local file.
4. To reload the WSDL into Pega Platform:
   1. In Dev Studio, open the Configure menu.
   2. Select Integration > Connectors > Create SOAP Integration.
   3. In the New SOAP integration wizard, select Upload WSDL from File.
   4. Complete the upload using the wizard prompts.

This is a design-time issue, not a run-time issue; therefore, clients only have to perform this workaround process once. Existing SOAP services should not be impacted; however, if clients modify an existing SOAP service definition by re-running the wizard, clients must reapply the workaround for Pega Platform to recognize the SOAP definition changes.  

Resolution

This issue will be addressed in the Pega Platform Patch Release 8.4.3.  Clients who upgrade to that version or later should not see this issue.

Native synchronization indicators for offline-enabled mobile apps

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

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

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.

Support for validations in Declare Expression rules

Pega Platform™ now correctly evaluates validations on target properties in Declare Expression rules. As a result, any validations defined on properties that have Declare Expression rules in previous releases, now work correctly. 

Upgrade impact

Any unintended validations on properties that have configured Declare Expression rules, both default and user-defined, might cause issues in an application upon saving work objects and data objects that refer to Declare Expression rules.

What steps are required to update the application to be compatible with this change? 

If you experience issues when saving objects, debug your application by setting the declareexp/target/validation/disable dynamic system setting to true. If your application works correctly after the change, it means that validations on Declare Expressions cause the issues. For your application to work correctly, analyze the log files and remove any unintended validations.

For more information, see Declare Expression rules.

Close button on a pop-up application update removed from App Studio

When you open an existing application that you created in previous releases without support for the Pega Express methodology, App Studio now displays a pop-up window to support Microjourneys™ without a Close button, to improve the usability of App Studio. 

Upgrade impact

The UI automation script might require a change if the script mentions clicking on the Close button.

What steps are required to update the application to be compatible with this change?

If you have a UI automation script that uses the Close button, update the UI automation script to delete reference to clicking on the Close button.

For more information, see Creating a Microjourney for customer success.

DocuSign integration support for OAuth 2.0

To comply with the latest DocuSign security standards, DocuSign integration in Pega Platform™ now supports OAuth 2.0 authentication. You can take advantage of this enhancement by downloading the DocuSign component from Pega Marketplace. For more information on configuring OAuth 2.0 authentication for your DocuSign integration, see Integrating DocuSign with Pega Platform.

Improving basic access control

Pega Platform™ has implemented a new basic access control (BAC) to protect your application from unauthorized server calls from otherwise authenticated users.

For more information, see Access Control Checks.

Upgrade impact

After you upgrade to Pega 8.5, all the functionality in the model configurations that use auto-generated controls and actions continues to work as before. However, you must secure any customized JavaScript in your application layer that makes AJAX (server) calls  by using registration or encryption mechanisms.

What steps are required to update the application to be compatible with this change?

After upgrade, to migrate custom JavaScript functionality, see Access Control Checks.