Published Release Notes

Twitter data sets no longer supported

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.

For Microsoft SQL Server deployments, change settings to create data types in Integration Designer

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.

Data entered in a new harness is lost after a sync operation

If you create a case in an offline-enabled application and enter data in a new harness, this data is lost after you click Submit and the sync operation takes place. For more information, see Offline capability and Enabling offline support for cases.