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.
Support for validations in Declare Expression rules
Valid from Pega Version 8.5
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
Valid from Pega Version 8.5
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.
Improving basic access control
Valid from Pega Version 8.5
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.
Search and Reporting does not index large items
Valid from Pega Version 8.5
When using the Search and Reporting (SRS) microservice in Pega Platform™ 8.5, you might encounter problems with indexing large out-of-the-box rules. The issue is not visible in Queue Processors, but you can access logs to verify which items the system does not index.
PegaWAI ruleset deprecated in 8.5
Valid from Pega Version 8.5
Accessibility functions that were contained in the PegaWAI ruleset are now integrated into the main Pega Platform™. Consequently, the user interface in your applications now features accessibility functions out of the box, so you no longer need to use the PegaWAI ruleset to ensure accessible behavior in your application.
For more information, see Building an accessible UI.
Support for building apps as Android App Bundles
Valid from Pega Version 8.6.1
As of August 2021, Google Play Store requires that you submit new apps in the Android App Bundle publishing format instead of the APK format. You can now build Pega mobile apps in the Android App Bundle format so that they comply with this new requirement.
For more information about generating installation packages for Pega mobile apps, see Generating installation packages. For more information about the Android App Bundle publishing format, see the Android for Developers documentation.
Tags disappear from Rich Text Editor source mode
Valid from Pega Version 8.5
When you use Rich Text Editor in HTML source mode, some tags disappear from the markup, which causes backward compatibility issues and data loss.
Cause
Pega Platform™ version 8.5.5 introduced the DOM Purifier security plugin. The plugin removes potentially vulnerable tags, including custom tags, from the raw HTML code in the Rich Text Editor source mode.
Workaround
You can disable the DOM Purifier plugin by adding the the window.disableDomPurifier = true
markup to the userWorkForm HTML fragment rule.
Alternatively, as of Pega Platform version 8.5.6, you can add a tag to the allow list by including the window.rteCustomAllowedTags = ['myCustomTag']
snippet in the userWorkForm HTML fragment rule.
In Pega Platform versions 8.5.6 to 8.6, the iframe
tag is added to the allow list by default.