Unable to create text analytics models when Java 2 Security is enabled
Valid from Pega Version 7.3
Security exceptions that prevent you from creating text analytics models are caused by the Java 2 Security feature that is enabled at the JVM level. This feature denies access to the text analytics resources that are required for text parsing functions.
Creating a text analytics model results in a failure because of a number of security-related exceptions, for example:
java.security.AccessControlException: Access denied ("java.lang.RuntimePermission""createSecurityManager")
The suggested approach for avoiding this problem is to use the text analytics models that are provided by default, for example, pySentimentModels, pyTelecomTaxonomy, and so on.
For more information, see Text Analyzer.
Expose properties in Decision Data Store
Valid from Pega Version 7.3.1
You can now expose properties in Cassandra-based Decision Data Store data sets. With this solution, you can update single properties in extended customer analytic records (XCAR) without having to update the full customer record.
For more information, see XCAR in Decision Data Store.
The Scratch Pad tool is no longer available
Valid from Pega Version 7.3.1
The Scratch Pad tool is no longer available. To add properties to a report from an end user portal, use the Data Explorer. The Data Explorer provides an efficient way to find a property or calculation to include as a column in a report.
For more information, see Data Explorer.
Email listeners no longer copy the email subject text to the email body
Valid from Pega Version 7.2.1
As of Pega® 7.2.1, email listeners no longer copy the email subject text to the email body when the body is empty. If your customer application expects text in the body of the email, the application might fail. You can configure email listeners to copy the subject text to the body by using the following Dynamic System Setting:
Owning Ruleset: Pega-IntSvcs
Purpose: email/copyBodyNoContent
Value: true
For more information, see Creating Dynamic System Settings.
Add new commands in the Facebook channel preview console
Valid from Pega Version 7.3.1
Now you can not only edit existing commands in the preview console for a Facebook channel but also add new command responses and associate them with intents. For example, you can add a new response command in the preview console in a case in which you entered a command and no response was found for the generated intent. This functionality gives you more control over the Facebook channel configuration and makes the preview console easier to use.
For more information, see Simulating a chatbot conversation.
Enhancements to bulk editing options for unversioned propositions
Valid from Pega Version 7.3.1
Bulk editing options for unversioned propositions have been enhanced to allow the use of Excel for editing. You can export and import unversioned propositions into Excel by using the Import wizard. Additionally, data types replace decision tables as the new storage format for unversioned propositions.
For more information, see Data type management and Proposition management enhancements.
Enhancements to PegaUnit test cases and test suites
Valid from Pega Version 7.3.1
Several enhancements have been made to PegaUnit test cases and test suites.
- You can now use advanced filters on the Automated Testing landing page and when you add test cases to a test suite to search for information.
- After you run a test case on the Edit Test Case form or a test suite on the Edit Test Suite form, the header now displays the expected and actual run-time values.
- You must now specify at least one assertion before you can save a test case.
- You can now compare a property to multiple values so that the assertion passes if any property meets the defined criteria.
- You can now use the is greater than and is less than comparators for date and date-time properties.
For more information about PegaUnit testing, see PegaUnit testing.
Execute Tests service now supports application name as a parameter
Valid from Pega Version 7.3.1
You can now use the application name and version as a parameter when running the Execute Tests service (REST API). When you build an application on Pega® Platform in a continuous delivery pipeline, you can use the Execute Tests service to validate the quality of the build by running PegaUnit test cases that are configured for the application.
For more information about the service, see Running PegaUnit test cases and test suites with the Execute Tests service in Pega 7.3.1.
Monitor application health on the Application Quality landing page
Valid from Pega Version 7.3.1
On the Application Quality landing page, you can view various quality-related data in one place so that you can monitor the quality of your application and correct any issues. The Application Quality landing page contains a summary of guardrails compliance, PegaUnit test coverage, and results of PegaUnit tests.
For more information, see Application Quality landing page.
View PegaUnit test reports
Valid from Pega Version 7.3.1
The Reports tab on the Automated Testing landing page contains tables and charts that display the percentage of rules on which PegaUnit test cases are configured, and the results of PegaUnit test execution. By looking at the data on this tab, you can see which tests failed and investigate them.
For more information, see Viewing PegaUnit reports.