Context-specific documentation is not available in express mode
Valid from Pega Version 7.1.9
Help topics that are opened from express mode display content that is specific to Designer Studio.
If your system is dedicated to applications that are developed in express mode exclusively, and you do not need Designer Studio help topics, you can set the Online Help URL field on the System Settings landing page to: https://pdn.pega.com/sites/default/files/help_p7e/procomhelpmain.htm. Alternatively, you can view the contextual help system for Pega 7 Express in a separate browser tab.
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.
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>.
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.
New dynamic setting to manage validation of hidden fields
Valid from Pega Version 8.6.4
Pega Platform™ version 8.6.4 introduces a new DSS setting for Theme Cosmos and other section-based applications. The validateHiddenField setting controls whether the application validates fields that you hide through visibility rules. By default, validateHiddenField is set to true
, which means that the application fields are validated for completeness even if they are not displayed in the form. You can also switch off this functionality by changing the setting value to false
.
For more information, see Managing field validation in hidden sections.