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.
Menu enhancements in the Facebook and WebChat user conversational channels
Valid from Pega Version 7.4
When you create a Facebook or WebChat channel interface to act as a Pega® Intelligent Virtual Assistant, you can use a Facebook-like generic template to display a rich user interface menu. You must use a data transform for the custom response to display this menu. You can use and modify the pyPopulateOutboundData data transform for this purpose.
For more information, see Adding custom responses for the Facebook channel and Adding custom responses for the WebChat channel.
Support for case references added to Pulse
Valid from Pega Version 7.4
You can now reference a case in a comment or post that you add to Pulse. By including a link in your message that opens a relevant work item, you can add context to a conversation.
For more information, see Enhancing a message in Pulse.
Node classification replaces NodeID-based configuration
Valid from Pega Version 7.4
For simpler cluster administration and better application resiliency, Pega® Platform is moving toward a node classification model. Although agents will continue to work by using NodeIDs for several upcoming releases, use node types instead of NodeID configuration for agents, listeners, and decisioning services for more efficient operations and upgrades.
For more information, see Node classification.
Aggregate data in interaction history summaries
Valid from Pega Version 7.4
You can now group, aggregate, and filter interaction history data in a single strategy component. By using interaction history summaries, you can create refined data sets that simplify strategy frameworks and accelerate decision-making. Aggregated data sets are easier to process, manage, and troubleshoot.
For more information, see Data Sources landing page
The worklist appears to be empty when you go back from an opened case in an offline-enabled mobile application
Valid from Pega Version 7.4
In a Pega® Platform offline-enabled application, when you go back to the worklist from an opened case, the worklist appears to be empty even though it contains cases. This issue will be fixed in the next release of Pega Platform. Only portals that use the key principles and design of the pyCaseWorker portal are supported in offline-enabled applications.
For more information, see Offline mobility guidelines.
Preflight optimization extended to actions
Valid from Pega Version 7.4
The preflight optimization process now excludes JavaScript for actions that are not used in the application. To enable preflight optimization, click Designer Studio > User Interface > Application readiness > Preflight optimization.
For more information, see Optimizing application load time.
New shape on the strategy canvas
Valid from Pega Version 7.4
The Strategy rule has been enhanced with the Embedded strategy shape, which simplifies the configuration of decisioning strategies that simultaneously apply to multiple types of audiences, for example, Devices, Households, and Subscribers. The Embedded strategy shape eliminates the need to switch between various classes to create a substrategy for each audience type that you want to target. Now, you can perform all configuration tasks on a single strategy canvas.
For more information, see Strategy components – Embedded strategy and Multilevel decisioning strategies.