Design-time limitations in express mode
Valid from Pega Version 7.1.9
Some limitations apply when you develop an enterprise application in express mode. At design time, some features are disabled or have limited options when you configure them in Designer Studio and switch to express mode. The use of these features does not restrict the run-time behavior of your application; however, you cannot change the configuration of these features unless you switch from express mode to Designer Studio.
For more information about each limitation and the recommended action to take, see the following information:
- Pega 7.2.2 Design-time limitations in express mode
- Pega 7.2.1 Design-time limitations in express mode
- Pega 7.2 Design-time limitations in express mode
- Pega 7.1.9 Design-time limitations in express mode
New types of data sets
Valid from Pega Version 7.1.9
There are three new types of data sets:
- Facebook - Required for connecting with the Facebook API
- Twitter - Required for connecting with the Twitter API
- YouTube - Required for connecting with the YouTube Data API
Use these data sets when you create instances of the Free Text Model rule and you want to analyze the text-based content on social media streams such as Facebook, Twitter, or YouTube.
Problem with truncating Decision Data Store data set
Valid from Pega Version 7.1.9
The Decision Data Store data set may cause timeout exceptions. This problem is caused by the Apache Cassandra database that waits until compaction tasks finish before it can truncate the data set.
operation for theRecommendation:
Repeat the
operation until it is successful.PegaDISTRIBUTION Manager (PDM) is no longer available
Valid from Pega Version 7.1.9
The PegaDISTRIBUTION Manager (PDM) is no longer available in the Pega 7 Platform. The related PDN articles and help topics have been archived.
Work attachment indexing fails with IBM SDK Java 6
Valid from Pega Version 7.1.7
Indexing of work attachments fails when you use IBM SDK Java 6 with Pega 7.1.7 through Pega 7.2. The workaround is to switch to IBM SDK Java 7 or Oracle JDK Java 1.6. You can also disable attachment indexing from the Search landing page; however, if you do this, you are not be able to search the content of attachments.
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.
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>.