PegaDATA connection settings now required in the prconfig.xml file
Valid from Pega Version 7.4
If you use the default prconfig.xml file that is included with Pega® Platform, and you have not removed the PegaDATA connection settings, no action is required. If you use a custom prconfig.xml file, for example, for running tests, ensure that the database connection settings for PegaDATA are not blank.
For more information about the connection settings, see PegaDATA connection settings in the prconfig.xml file.
Add message header fields to the service email for Pulse email replies
Valid from Pega Version 7.4
The pzCreatePulseReply service email rule now has these additional fields in the message header: Message–ID, In–Reply–To, and References. As a result, the system interacts with email clients by using email headers when users reply to Pulse emails. If you configured a service email for replies to Pulse email notifications, add these fields to the service email to allow the system to post the replies in Pulse. If you are creating a service email, ensure that the message header and data have the same values as the values in pzCreatePulseReply.
For more information, see Enabling users to respond to Pulse email notifications.
Support for multiple attachments added to Pulse
Valid from Pega Version 7.4
You can now upload more than one attachment to posts and comments in Pulse. Because Pulse maintains the continuity of attachments in posts, email messages, and email notifications, you can use it to quickly follow conversations in a case.
For more information about the features that Pulse supports, see Communicating with Pulse.
Manage propositions in multitenant environments
Valid from Pega Version 7.4
Proposition Management is now supported in multitenant environments of Pega® Platform. The DisablePropCache Dynamic System Setting switches off the use of a proposition cache. When you import propositions in strategies, you can import only versioned propositions (Decision Data rules). Unversioned propositions are not supported under this setting, but these can be converted to versioned propositions.
For more information, see Unversioned propositions, Synchronization of the proposition cache, and Converting groups with unversioned propositions.
VTable dispatch mechanism for HTML control execution improves performance
Valid from Pega Version 7.4
Pega® Platform now uses an optimized VTable dispatch mechanism to manage rule execution for the Text Input and Formatted Text Input controls. This change improves performance by eliminating the dependency between stream rules and HTML controls during rule assembly. Disabling this feature will have a negative effect on performance and is not recommended. However, you can disable this feature by adding the following configuration parameter:
Name: assembly/section/control/vtable
Value: false
Layout groups and design templates
Valid from Pega Version 7.4
On the Design tab of the Section form in Designer Studio, you can use a layout group to display closely related information by using accordion, menu, stacked, or tab navigation elements. You can then create a templated region that is based on the layout group. For example, you can use this type of region to enable users to add, reorder, or remove tabs from screens at run time in Pega® Express.
For more information, see Creating a templated region based on a layout group and Creating a templated region based on a layout group.
Actions for included sections
Valid from Pega Version 7.4
On the Design tab of the Section form in Designer Studio, you can include a section inside another section. To enhance reuse possibilities, you can also add an action to an included section. For example, you might specify an action set that automatically displays a smart tip when a user hovers over the included section in one case, but specify a different action set for the same included section in another form or even in another application.
For more information, see Adding actions to included sections.
Specify styles at run time in Pega Express
Valid from Pega Version 7.4
At run time in Pega® Express, you can now apply styling to many controls. Styling options vary from one control to another. For example, when you style a Dropdown control, you can specify text color, background fill and color, and border width and color. When you style controls directly in Pega Express, rather than switching to Designer Studio to modify the application skin, you can save development time.
For more information, see Styling controls at run time in Pega Express.
Configure the window size at run time in event strategies
Valid from Pega Version 7.4
You can now configure an Event Strategy rule to dynamically define the window size at run time by using a property value of the incoming record. To configure the window shape for dynamic size setting, you can use any property from the inheritance path that is available to the event strategy. This enhancement provides greater flexibility for strategy designers and broadens the scope of business scenarios in which event strategies can be applied.
For more information, see Event Strategy rule form - Completing the Event Strategy tab and Dynamic window size behavior.
Support for mobile mashup demo app in the Mashup channel configuration
Valid from Pega Version 7.4
When you configure the Mashup channel interface in Pega® Platform, you can now also test your cases in a mashup demo app. By testing, you can improve customer self-service because you can immediately visualize how your cases are extended into a native mobile app. During configuration, you must download the Pega Mashup Preview mobile app from the Apple App Store or Google Play and scan the QR code by using the app.
For more information, see Configuring the Mashup channel.