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.