Published Release Notes

Create and view application settings in App Studio

View your application settings on the new Application settings landing page in App Studio. The landing page displays the categories that you specified for your application settings. If you did not specify a category for an application setting, the application setting appears in the Uncategorized category. Additionally, when you create a new data type, the Data type wizard automatically creates an application setting for the base URLs and the authentication profile. On the Environment settings page, you can edit the application setting to specify a new name or category or accept the default values.

For more information, see Viewing application settings in App Studio and Preparing your data for production.

Upgrade impact

After a successful upgrade, you see the new Application Settings option under Settings in App Studio. 

What steps are required to update the application to be compatible with this change?

1. If the label (Application Settings) conflicts with your existing extension, change the label by overriding the following field value:
   PEGA-EXT- EXPEXPLORER-SETTINGS-APPSETTINGS PYCAPTIONIEXTENSION!LABEL
2. If you need to disable the landing page and prevent it from appearing in App studio, change the following toggle to No:
   PegaRULES: DisableSettingsLandingPage

New interaction history attribute

Pega^® Platform 7.4 introduces the pySubjectType attribute that is used in interaction history aggregations. This attribute is populated for interaction history records that were created in release 7.4. For records that originated in earlier releases, the attribute must be set in the following scenarios:

• Single-level decisioning frameworks that use interaction history.
• Multi-level decisioning frameworks where interaction history is used by two or more levels of strategies that are defined on different classes.

For the single-level scenario, configure the Dynamic System Setting that sets the pySubjectType attribute when your framework reads interaction history records. The value of this Dynamic System Setting becomes the name of the customer class.

For the multi-level scenario, update the database table for all strategy levels manually. For each level, make sure that the value in the Subject Type column is set to the name of the class for the corresponding strategy. For example, the value for the top level strategy should be set to the name of the class of that strategy.

For more information about interaction history aggregations, see Data Sources landing page

For more information about multi-line strategies and contexts, see Strategy components - Embedded strategy

Automatic management of run-time context for background processing

Management of system run-time context is now automatic. You no longer need to manually modify the AsyncProcessor requestor type context to make a queue processor or job scheduler work after importing or upgrading an application. Additionally, you do not need to manually modify the AsyncProcessor requestor type context to make new queue processors and job schedulers work.

For more information, see System general landing page and Automating the runtime context management of background processes.

Upgrade impact

After upgrade, you manage the runtime context of your background processing in System Runtime Context instead of in the deprecated AsyncProcessor requestor type.

What steps are required to update the application to be compatible with this change?

Select the Include in background processing option in the Advanced section of the application rule form for all applications that use background processing (such as Job Schedulers and Queue Processing). When this option is enabled, the system automatically includes the rulesets (for the application and its components) in System Runtime Context used for resolving and running Queue Processors and Job Schedulers. Also, when the option is enabled, the application is placed on the System Runtime Context list during application rule saves (such as during application import and migration).

Improved identification and handling of code assembly errors

Code assembly error logs are now more meaningful and help you identify root causes with better accuracy. Pega Platform™ now also invalidates erroneous assembly to facilitate successful reassembly when the code is accessed again. For example, if a section is not correctly assembled when a user first signs in to the system, the application attempts to reassemble that section the next time a user signs in. In this way, you can avoid lingering issues and improve stability.

getRuleMessage APIs no longer prepend asterisks

The Public APIs getRuleMessage(String aMsgDescr) and getRuleMessage(String aMsgDescr,String messageClass) no longer prepend asterisks ("**") to the message description when they fail to find a Rule-Message instance whose name matches the input message description. For information about these APIs, access the Public API documentation in Designer Studio by clicking Resources > Engine API.

Stakeholder management extended to case followers

You can now control which users follow a case. By actively involving the people with relevant skills and roles in your application, you can resolve cases more quickly.

For more information, see Case followers.

New capabilities of the rich text editor

The enhanced rich text editor has a new plug-in that helps the users skip a few configuration screens by uploading image files directly from the file system. When they copy and paste content from a word processor or a spreadsheet, the text retains the original formatting. The developers can now configure all toolbar options, such as bulleting or font formatting, so the users can focus only on the tools that they need and work more efficiently.

For more information, see Selecting the property for a Rich text editor control.

Support for multiple work queues in the Email Manager portal

Pega Email Bot™ now provides multiple work queues in the Email Manager portal. With this functionality, operators, such as customer service representatives, can now triage cases more efficiently by selecting different work queues. Operators have access to work queues only for the current Pega Platform™ application.

For more information, see Email Manager portal.

Enhanced tables in Cosmos React UI

The Pega Platform™ Cosmos React UI environment now includes improved tables. The updated tables use a revamped graphic design and support a number of new run-time behaviors, including column freezing and advanced filtering. The added features improve the user experience by giving case workers more control over data in tables, while the revised architecture enhances efficiency and reliability.

Prediction Studio notifications

Prediction Studio now displays notifications when adaptive or predictive models encounter problems. For example, if the performance of a model decreases suddenly, a notification appears, which you can use to immediately investigate the cause of the problem.

For more information, see Accessing Prediction Studio notifications and Prediction Studio notification types.