Nodes in a cluster do not see each other for Docker, multiple VMs, or multiple NICs setup
Valid from Pega Version 7.3
If a cluster is set up in Docker, or uses separate virtual machines (VMs) or multiple network interfaces, you must set the public address in the prconfig.xml file for each Pega® Platform node to avoid problems with node clustering. Add the <env name=”identification/cluster/public/address” value=”IP address”/> setting to specify the public address that is used by each node.
Pega Survey documentation refers to deprecated field
Valid from Pega Version 7.2.1
The documentation for Pega® Survey refers to the Answer Layout field on the Complex Question form, but this field is no longer supported. For more information about the question layout formats that Pega Survey supports, see Pega Survey.
Security fields in JFrog Artifactory repository do not work
Valid from Pega Version 7.3
The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not implemented. In the Pega™ Platform 7.3 Designer Studio help, disregard the optional Security section in step 4 of the Configuring a JFrog Artifactory or Amazon S3 repository connection help topic, and disregard the optional Security section in step 5 of the Creating a repository configuration help topic in the 7.3.1 Designer Studio help.
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.
Experimental high-speed data page support
Valid from Pega Version 7.3
An experimental implementation of high-speed, read-only data pages is available. This implementation is useful when data pages are used to hold static data that is used repeatedly. You can enable this feature for a specific read-only data page from the Load Management tab of the data page rule form by clicking Enable high-performance read-only data page. This feature does not support full clipboard page functionality; use with caution.
The following functionality is supported:
- Basic page and property access (read and write properties) for all normal data types
- Hierarchical data page structure (pages within pages)
- Dictionary validation mode
- Read-only data pages
The following functionality is not supported:
- Declarative rules
- Page messages
- Complex property references
- Saving pages to a database
- API access to the data page
Gadget configuration by using IAC gateway console is no longer supported
Valid from Pega Version 7.2.1
The Internet Application Composer (IAC) gateway was deprecated in Pega Platform™ 7.2.1 and is no longer supported. The IAC was used to embed a Pega Platform application, such as a gadget, on the pages of a web application that was located on your intranet, extranet, or internet site.
Upgrade impact
After an upgrade to Pega Platform 8.5, the configuration of gadgets through the IAC gateway console is no longer supported.
What steps are required to update the application to be compatible with this change?
To make subsequent changes to your current web mashup, use Pega Web Mashup.
For more information, see Tutorial: Creating a mashup with Pega Web Mashup.
New dynamic setting to manage validation of hidden fields
Valid from Pega Version 8.6.4
Pega Platform™ version 8.6.4 introduces a new DSS setting for Theme Cosmos and other section-based applications. The validateHiddenField setting controls whether the application validates fields that you hide through visibility rules. By default, validateHiddenField is set to true, which means that the application fields are validated for completeness even if they are not displayed in the form. You can also switch off this functionality by changing the setting value to false.
For more information, see Managing field validation in hidden sections.