New property pxSaveDateTime
Valid from Pega Version 7.1.8
A new property, pxSaveDateTime, records the date and the time that an instance was saved with business changes to the database. This property is always used when an instance is saved, whether you are creating an instance or updating an existing instance. This property is not updated when an instance is moved from one system to another, and it is not updated during certain system management operations that do not change the content of the instance, such as column exposure.
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.
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.
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.
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.