Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

JavaMail API upgrade has potential SMTP configuration error

Valid from Pega Version 7.1.8

The JavaMail API has been upgraded from 1.4.1 to 1.5.2 in this release. This improvement provides greater compatibility and secure connectivity with leading industry email servers.

During the upgrade process, there is a known issue for some configurations of email servers, including Microsoft Exchange Server, that requires the use of an additional setting. After upgrading to this release, if you experience authentication failures when attempting to send email or test SMTP connectivity, do one of the following:

  • Recommended: Review the Microsoft Exchange email server settings to ensure proper configuration for SMTP authentication. In some cases, the use of port 587 instead of the traditional default SMTP port 25 has been shown to address this issue.
  • Create the following Dynamic System Setting with the value "true," and then restart email listeners:

Owning Ruleset: Pega-IntegrationEngine

Setting Purpose: javamail/NoAuthMechanismsRetry

After any email server configuration or upgrade, it is recommended that email listeners are re-tested without using this Dynamic System Setting.

See About Email Account data instances for information on configuring email account records.

Creating data page unit tests in Internet Explorer 8

Valid from Pega Version 7.1.8

When creating data page unit tests, selecting a parent property does not automatically select the child properties when using Internet Explorer 8.

Page and page list properties to be included in a data page unit test are selected on the Create test screen by selecting a check box next to the property name. Normally, selecting the check box of a parent property automatically selects all subsequent child properties as well. When using Internet Explorer 8, child properties are not automatically selected when the parent property's check box is selected.

The solution requires selecting all of the desired child properties individually. Select the check box next to each child property to include it in the data page unit test.

Schema not found error when importing a Rule-Admin-Product file

Valid from Pega Version 7.1.8

If you import a Rule-Admin-Product file (RAP) file that includes a schema that has a view, grammar parsing changes can mean that the Pega 7 Platform is unable to find the schema.

To enable the Pega 7 Platform to find the schema:

  1. Review the error message that indicates that the schema was not found and identify the following items:
    • The name of the schema that is causing the error
    • The table name in the format: wrong_schema_name.table_name...
    • The DDL that the Pega 7 Platform is trying to apply
  2. Use the table name to identify the correct schema name in your system. This schema is usually your data schema, but might also be an external database.
  3. Download the DDL.
  4. Correct the schema name and save the DDL.
  5. Manually apply the DDL.

WebSphere log error with Java 8 for Enterprise JavaBeans

Valid from Pega Version 7.1.8

For environments that are deployed by using Java 8 on IBM WebSphere Application Server version 8.5.5.9 through the last 8.5.5.x fix pack, the log might report that a class was not found when the application server attempts to start Enterprise JavaBeans. If Java EE functionality is not needed, no further action is required. However, to use Enterprise JavaBeans, see WebSphere log error with Java 8 for Enterprise JavaBeans.

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.

Precision of Oracle Timestamp property when using RDB-Save

Valid from Pega Version 7.1.8

DateTime properties that are mapped to an Oracle Timestamp column will experience a loss of precision when they are saved using the RDB-Save method. When you use RDB-Save for an Oracle Timestamp, precision will be accurate to the second. For example, a value of 20171119T124745.006 will be saved as 20171119T124745. When you use Obj-Save, precision will be accurate to the millisecond. For more information, see DateTime property mapping in Oracle for Pega 7.

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us