Data synchronization does not resume after mobile app restart
Valid from Pega Version 8.3
If an offline-enabled mobile app that you build with Pega Infinity Mobile Client™ is stopped during an initial data synchronization session, the data synchronization does not resume when the mobile app is restarted. Users must not stop the mobile app before initial data synchronization finishes.
For more information about data synchronization, see Offline capability and Guidelines for creating an offline-enabled application.
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.
Node description cannot match application server node name
Valid from Pega Version 6.3 SP1
A node's Short Description should not be the same value as the application server node name. If the node's Short Description is changed to be the same value as the application server node name, then the node description is automatically changed back to the original value after a system restart.
Twitter data sets no longer supported
Valid from Pega Version 7.1.9
Twitter is deprecating several APIs, which will disrupt the Twitter data set functionality. Twitter data sets will not be able to fetch any tweets or direct messages. This issue affects all applications that use Twitter data sets to connect to social (mainly Pega Customer Service applications).
This change applies to the current and earlier releases of Pega Platform™ that make use of Twitter data sets and it impacts all environments, including Pixar, VM, and Pega Labs instances.
Twitter connectors will be fully functional at a later date. For now, the best practice is to de-emphasize social media in your data sets.
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.
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.
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.