Screenshot generation runs on local client
Valid from Pega Version 7.1.8
If you generate screenshots to include in your application document, this process still runs on your local client. Additionally, you are still required to use Internet Explorer to use this feature.
Warning message when opening server-generated documents
Valid from Pega Version 7.1.8
Depending on your system configuration, the following warning message might be displayed when you open a document that was generated on the server.
If you click
, certain content (for example, Table of Contents) is not populated in the document. Instead, click and save the document.The warning message that displays
Derby databases are no longer supported
Valid from Pega Version 7.1.8
Previously, an embedded Derby database could be used as a file system. This setup was configured by setting storage/class/<<filesystem>>/type to "embedded" in the prconfig
file.
After upgrading, storage types that are specified as "embedded" now default to the local file system.
Custom database (DB) triggers are dropped during upgrade
Valid from Pega Version 7.1.8
The latest version of Pega 7 improves performance by no longer using database triggers to assist with System Pulse and Data-Rule-Summary processing, which is now done within the Pega 7 engine. As a result, DB triggers are no longer installed on either the pr_sys_updatescache
or pr4_rule_vw
tables.
When upgrading to the latest version of Pega 7, if you had previously implemented a custom database (DB) trigger on these tables, or a custom DB trigger that refers to these tables, it is removed during the upgrade process. No custom triggers are removed unless they reference these tables.
If you have custom DB triggers that reference the pr_sys_updatescache
or pr4_rule_vw
tables and perform other processing, those triggers must be reimplemented. When doing so, you must be careful to not modify the pr_sys_updatescache
or pr4_rule_vw tables
.
For more information, see Startup check removes custom DB triggers.
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.
Number and text input controls on Android devices may not display the correct keyboard
Valid from Pega Version 7.1.8
When running a Pega 7 application on a device using the Android operating system, pxNumber and pxTextInput controls may not display when using the desired on-screen keyboard. This happens when the number or text input type is set to number
.
At design time, the input type is selected in the Editable Format section of the Presentation tab in the Cell Properties panel for a pxNumber or pxTextInput control. Due to a known limitation in some versions of the Android OS running on some devices, the keyboard displayed at run time may not support entry of decimal values when a Number type keyboard is specified.
To resolve this issue, use the Phone
type when numbers with decimal values may be required. Using the Phone
type displays a numerical phone keyboard. The Android phone keyboard includes both commas and periods so that decimals may be entered.
The Phone type selected in the Presentation tab of a Number control
Note that this issue only occurs on Android devices. It is recommended that applications for iOS continue to use type=“Number”.
Deprecated rule types
Valid from Pega Version 7.1.8
The following rule types have been deprecated as of the Pega 7.1.8 release:
- Form
- Hierarchy
- Service COM
- Service BPEL
- Connect BPEL
- Parse Transform
- Parse Transform Collection
- Parse Infer
For more information, including suggested alternate rule types, see the help topic Deprecated features.
The Create Build button appears grayed out when configuring and building a mobile application
Valid from Pega Version 7.1.8
When you attempt to configure and build your Android or iOS mobile application from the Mobile tab, the button might appear dimmed. This issue occurs if any of the access roles in the access group were cloned from the PegaRULES:SysAdm4 access role.
Refer to Troubleshooting Pega Mobile Client to learn how to fix this issue in your application.
Decision Data Store data sets can be used only on DNodes
Valid from Pega Version 7.1.8
Data flows that contain Decision Data Store data sets as the primary or secondary source must be created and executed only on DNodes.
Data flows are not restarted automatically after application server restart
Valid from Pega Version 7.1.8
When you restart the application server or the Pega 7 server, you stop the execution of your data flows. The interrupted batch and real-time runs are marked as Failed.
Recommendation:
- Go to the > > > > tab and start the failed batch runs.
-
Go to the
> > > > tab and activate the failed real-time runs.