X-Forwarded-Host field is optional for HTTP proxy servers
Valid from Pega Version 7.3
Prior to Pega® Platform 7.3, the X-Forwarded-Proto and X-Forwarded-Host fields were both required to deploy Pega Platform instances behind an HTTP proxy server. Some proxy servers or load balancers (for example, Amazon ELB) do not support the X-Forwarded-Hostfield. Starting with Pega 7.3, only the X-Forwarded-Proto field is required. For more information, see Deployment behind a reverse proxy.
Unable to create text analytics models when Java 2 Security is enabled
Valid from Pega Version 7.3
Security exceptions that prevent you from creating text analytics models are caused by the Java 2 Security feature that is enabled at the JVM level. This feature denies access to the text analytics resources that are required for text parsing functions.
Creating a text analytics model results in a failure because of a number of security-related exceptions, for example:
java.security.AccessControlException: Access denied ("java.lang.RuntimePermission""createSecurityManager")
The suggested approach for avoiding this problem is to use the text analytics models that are provided by default, for example, pySentimentModels, pyTelecomTaxonomy, and so on.
For more information, see Text Analyzer.
No video controllers displayed on Android 4.3 and earlier versions
Valid from Pega Version 7.3
When you preview a video clip within Pega® Mobile Client on a mobile device that runs Android 4.3 or earlier versions, video controllers are not displayed in full-screen mode.
Upgrades and updates from Pega 7.3 on MSSQL fail with column name mismatch
Valid from Pega Version 7.3
This failure applies only to upgrades and updates from Pega® Platform 7.3 on systems running Microsoft® SQL Server®. In Pega 7.3, the capitalization for the column name pc_work_agile.pzPvStream is incorrect. The correct capitalization is pzPVStream. To prevent upgrade and update failures, before you upgrade or update, run the following command from the Microsoft SQL Server Management Studio (SSMS) to rename the column:
EXEC sp_rename ‘data-schema-name.pc_work_agile.pzPvStream', 'pzPVStream', 'COLUMN'
Reports on pc_work_agile table fail in Pega 7.3 on MSSQL
Valid from Pega Version 7.3
This failure applies only to Pega® Platform 7.3 on systems running Microsoft SQL Server. In Pega 7.3, the capitalization for the column name pc_work_agile.pzPvStream is incorrect. The correct capitalization is pzPVStream. To prevent reporting failures on the pc_work_agile table, run the following command from the Microsoft SQL Server Management Studio (SSMS) to rename the column after you install Pega 7.3:
EXEC sp_rename ‘data-schema-name.pc_work_agile.pzPvStream', 'pzPVStream', 'COLUMN'
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.
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.
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