Extract marker file not created at startup
Valid from Pega Version 7.2.1
The extract marker file (PegaRULES_Extract_Marker.txt) is not created at startup, because the rule utility libraries no longer need it. If you used to use the extract marker file to clear the static content file-based cache, to look up lists, or to control starting activities with web nodes, you can delete the contents of the PegaRULES temporary directory instead.
The UpdateAdaptiveModels agent causes an exception after Pega 7.2 to 7.2.1 upgrade
Valid from Pega Version 7.2.1
After the Pega 7 Platform is upgraded from version 7.2 to 7.2.1, the log files might show an error that is caused by the UpdateAdaptiveModels agent. This agent is enabled by default and is responsible for updating scoring models in the Pega 7 Platform. If you use adaptive models in your solution, you can avoid this error by configuring the Adaptive Decision Manager service. If you do not use adaptive models, disable the UpdateAdaptiveModels agent.
For more information, see Configuring the Adaptive Decision Manager service and Pega-DecisionEngine agents.
Reconfiguration of the Adaptive Decision Manager service after upgrade to Pega 7.2.1
Valid from Pega Version 7.2.1
After you upgrade the Pega 7 Platform to version 7.2.1, you need to reconfigure the Adaptive Decision Manager service. Beginning with Pega 7.2.1, the Adaptive Decision Management (ADM) service is native to the Pega 7 Platform and is supported by the Decision data node infrastructure.
For more information, see Services landing page.
Upgrade/update fails if PostGIS is applied to PegaRULES or PegaDATA schema
Valid from Pega Version 7.2.1
If you use the PostGIS extension to a PostgreSQL database, upgrading or updating the Pega 7 Platform fails if the extension has been applied to either the PegaRULES or PegaDATA schema. PostGIS can be applied to any other schema.
Primary key constraint error when using JBoss
Valid from Pega Version 7.1.9
A primary key constraint violation exception might occur in the following situation: you use JBoss EAP 6.4 and SQL Server 2012 with a JDBC 4 driver, and you use two or more file listeners or JMS MDB listeners with concurrent threads that create work objects that use multiple files. If a primary key constraint violation exception occurs in this situation, update the data source configuration file to set the jta parameter to true. For example, set <datasource jta="true" jndi-name-"java:/jdbc/PegaRULES>.
Email listeners no longer copy the email subject text to the email body
Valid from Pega Version 7.2.1
As of Pega® 7.2.1, email listeners no longer copy the email subject text to the email body when the body is empty. If your customer application expects text in the body of the email, the application might fail. You can configure email listeners to copy the subject text to the body by using the following Dynamic System Setting:
Owning Ruleset: Pega-IntSvcs
Purpose: email/copyBodyNoContent
Value: true
For more information, see Creating Dynamic System Settings.
Pega Survey documentation refers to deprecated field
Valid from Pega Version 7.2.1
The documentation for Pega® Survey refers to the Answer Layout field on the Complex Question form, but this field is no longer supported. For more information about the question layout formats that Pega Survey supports, see Pega Survey.
Twitter data sets no longer supported
Valid from Pega Version 7.1.9
Twitter is deprecating several APIs, which will disrupt the Twitter data set functionality. Twitter data sets will not be able to fetch any tweets or direct messages. This issue affects all applications that use Twitter data sets to connect to social (mainly Pega Customer Service applications).
This change applies to the current and earlier releases of Pega Platform™ that make use of Twitter data sets and it impacts all environments, including Pixar, VM, and Pega Labs instances.
Twitter connectors will be fully functional at a later date. For now, the best practice is to de-emphasize social media in your data sets.