Updates no longer require redeploying the prweb.war file or the application server-specific EAR file
Valid from Pega Version 7.1.7
Updating from Pega 7.1.7 to later versions of Pega 7 no longer requires that you redeploy the prweb.war file or the application server-specific EAR file.
Note that upgrades from versions prior to Pega 7.1.7 still require that you redeploy these files.
The System Management Application is supported only on Microsoft Internet Explorer
Valid from Pega Version 7.1.7
Microsoft Internet Explorer (IE) is required for the System Management Application (SMA). No other browser is supported.
Service responses in HTTP and REST connectors are no longer modified
Valid from Pega Version 7.1.7
The Pega 7.1.8 release correctly leaves form service responses for HTTP and REST connectors unmodified. Upgrade to this release if you experience a problem in Pega 7.1.7 where service responses for HTTP and REST connectors are modified when the declared type in the Content-Type header is application/x-www-form-urlencoded. In this case, the responses were modified to a base 64 representation of the bytes in the string. In Pega 7.1.8, responses of type application/x-www-form-urlencoded are mapped to the property designated on the Connector record.
Create and modify tenants only from the Tenant Management landing pages or SOAP operations
Valid from Pega Version 7.1.7
When creating or modifying tenants, do not use any of the following methods:
- Creating a new tenant definition from the Data-Admin-Tenant list
- Using the Save As feature to create a tenant from an existing tenant
- Creating a tenant from the rule form from the menu
Although these methods might appear to work, the resulting tenants have no associated metadata and are not valid. Always use landing pages or SOAP operations to create or modify tenants.
Work attachment indexing fails with IBM SDK Java 6
Valid from Pega Version 7.1.7
Indexing of work attachments fails when you use IBM SDK Java 6 with Pega 7.1.7 through Pega 7.2. The workaround is to switch to IBM SDK Java 7 or Oracle JDK Java 1.6. You can also disable attachment indexing from the Search landing page; however, if you do this, you are not be able to search the content of attachments.
Agents not running after update of EAR-based deployment
Valid from Pega Version 7.1.7
If you update an EAR-file deployment and your update meets both of the following criteria, you must redeploy the prpc_*.ear file for your application server after you complete the update to avoid agent-related errors:
- Updating from Pega 7.1.7, Pega 7.1.8, or Pega 7.1.9
- Updating to Pega 7.1.10, 7.1.11, 7.2, or 7.2.1
If you do not redeploy the prpc_*.ear file, you will see the agent-related issues that are described in the support article Agents are not running.
For information about redeploying, see the Pega 7 Platform Update Guide for your target version of the Pega 7 Platform.