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.
New alert for distinct values query
Valid from Pega Version 7.3.1
The PEGA0093 alert identifies performance issues when a distinct values query from virtual reports or the getDistinctValuesForProperty
API take longer than the threshold. For more information, see PEGA0093: Distinct values query took more than the threshold.
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.