Published Release Notes

X-Forwarded-Host field is optional for HTTP proxy servers

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

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

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

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

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

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.

Internal rules in search results and explorers

Using old: is no longer supported in search. You can include internal rules in search results and make them available in the Application and Records explorers. Include internal rules in search results either by adding the PegaDevelopmentruleset to your application or by clicking the Enable diagnostic features option in your operator preferences.

Ability to include all properties in search results

You can now include all properties in a class in search results so that they can be used in report filtering. When the Enable search results for all properties option is selected on the Custom Search Properties rule form, all top level and embedded page scalar properties for the class are indexed and returned in search results, and all embedded page list, page group, value list, and value group properties for the class are indexed but not returned in search results. Selecting this option might affect performance.

In addition, by default, properties defined in the Data-Tag-RelevantRecord instance for a class are indexed and returned in search results and do not need to be explicitly configured.

You must reindex search after selecting or clearing Enable search results for all properties and after changing the properties that are defined in the Data-Tag-RelevantRecord instance.

For more information, see Specifying custom search properties.

SAML single sign-on is easier to configure

Implementing SAML single sign-on (SSO) login authentication in your application is now less complex. You can now configure most requirements that used custom activities or Java code in previous releases from the Authentication services form.

For more information, see Creating an authentication service.

Support for controlling binary file upload in Pega Mobile Client

The Client Store API of Pega^® Mobile Client has been modified so that you can suspend and resume the process of uploading binary files to the server. You can also check the state of the file uploading process. As a result, custom mobile app users can process their work items without having to wait for the synchronization process to finish.

For more information, see Pega Mobile Client API methods for controlling binary data upload and Client Store API.