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.
Naming pattern changed for file data sets
Valid from Pega Version 8.6.3
File data sets are used to import from and export data to a file repository. In case of data export, prior to version 8.6.3, the first file exported had the same file name that was provided by the user in the data set, and any subsequent file exported to the repository had a unique identifier appended to it. Starting in Pega Platform version 8.6.3, each file has a unique identifier, automatically generated based on the data flow node, thread ID, and timestamp.
Upgrade impact
If your process to consume output files expects files with a specific name, it may not be able to process the resulting files correctly.
What steps are required to update the application to be compatible with this change?
If you have configured the process before updating to Pega Platform version 8.6.3, but the exported files are no longer recognized by downstream processing logic after the upgrade, ensure that the downstream tool is configured to recognize the files by a pattern rather than the full name. For example, when referring to files exported to the repository, use the * character to indicate a pattern instead of using the full file name. For example, use Export*.csv to refer to the files.
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.