Cannot create new data tables after update
Valid from Pega Version 7.1.7
Data tables have been replaced by a new local data storage format. You can upgrade old-style data tables to use the new local data storage format, but the new format is not compatible with earlier versions of Pega 7 in which data tables could be created.
You can still edit legacy data tables by using the old data table functionality. However, to create new data tables, you must use the Data Explorer and Data Designer.
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.
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.
Use fast processing option does not work
Valid from Pega Version 7.3.1
The Use fast processing option on Connect REST and Service REST rule forms does not work unless you obtain the HFix-43000 hotfix from Global Customer Service.
Use the following data model guidelines when using fast processing:
- The JSON property names and the clipboard property names must match.
- The JSON tree structure and the clipboard tree structure must be similar.
- The scalar arrays in JSON must be mapped to the clipboard as page lists.
- Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.
In addition, page groups, value groups, and Java objects are not supported by fast processing.
For Microsoft SQL Server deployments, change settings to create data types in Integration Designer
Valid from Pega Version 8.1
For on-premises deployments that use Microsoft SQL Server, set the Pega-Reporting/reporting/useMergeHintForRRquery dynamic system setting to true. If you do not configure this setting, you might not be able to create a new data type in Integration Designer that uses Pega as the system of record. Configure the setting as follows:
- Owning ruleset: Pega-Reporting
- Setting purpose: reporting/useMergeHintForRRquery
- Value: true
For more information about configuring dynamic system settings, see Creating a dynamic system setting.