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>.
View status of custom search indexes
Valid from Pega Version 8.1
Custom search indexes are special purpose indexes that are created and managed outside of Pega Platform™. You can view the status of custom search indexes on the Search landing page to see whether they are complete. This information is useful for troubleshooting and can help you determine whether to rebuild the index.
For more information, see Checking search index status.
Job Scheduler and Queue Processor rules replace agents
Valid from Pega Version 8.1
The Job Scheduler rule and the Queue Processor rule replace agents and improve background processing. The Job Scheduler rule is used for recurring or scheduled tasks, such as sending summary emails on weekdays. This rule can be run on all nodes or on specific node types according to your customized pattern. The Queue Processor rule is used for tasks with no recurrence-based pattern. It provides scalability and capability for immediate or delayed message processing, such as submitting status changes to an external system. You can use a standard queue processor or a dedicated queue processor, depending on your processing needs.
Pega Platform™ provides a set of default queue processors and job schedulers. Corresponding agents are no longer available.
For more information about Job Scheduler and Queue Processor rules, see Job Scheduler, Replacing an agent with a Job Scheduler rule, Queue Processor, Replacing an agent with a Queue Processor rule.
Improve application test coverage by running multiple sessions
Valid from Pega Version 8.1
You can improve the test coverage of your application by using a new test coverage method - Application Coverage. Multiple users can perform coverage sessions which are aggregated into a single report. By using report metrics that show the number of rules that are covered and are not covered by tests, developers can identify which areas of the application need more test coverage.
For more information, see the Test Coverage landing page.
Security fields in JFrog Artifactory repository rule form removed
Valid from Pega Version 8.1
The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not functional in Pega Platform™ 7.3, 7.3.1, and 7.4. This section has been removed from the JFrog Artifactory repository rule form in Pega Platform 8.1.