Limited question and answer formats in new surveys
Valid from Pega Version 7.4
Complex questions and some answer formats for simple questions, such as attachment, are not supported by the new surveys that you create. Although you can create stand-alone questions in your survey library that use these formats, you can add these questions to legacy surveys only.
For more information about supported answer formats, see Answer formats for questions in a survey.
The worklist appears to be empty when you go back from an opened case in an offline-enabled mobile application
Valid from Pega Version 7.4
In a Pega® Platform offline-enabled application, when you go back to the worklist from an opened case, the worklist appears to be empty even though it contains cases. This issue will be fixed in the next release of Pega Platform. Only portals that use the key principles and design of the pyCaseWorker portal are supported in offline-enabled applications.
For more information, see Offline mobility guidelines.
Browser unresponsive when logging in to Designer Studio
Valid from Pega Version 7.4
The What's new in 7.4 widget on the Designer Studio home page uses WebGL to render its background animation. If your browser is running on a virtual machine without hardware acceleration, your browser might become unresponsive because of this widget. Click the Hide this until next release button to remove the widget. At your next login, the widget will not be displayed.
Known issue: SAML IdP import uses only the last certificate
Valid from Pega Version 7.4
When you configure the identity provider for a SAML SSO authentication service, the backing keystore rule for the verification certificate is created with only the last certificate from the IdP metadata, instead of using all of the certificates.
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.
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.