Published Release Notes

Include videos within sections

You can include videos within sections to build an interactive user experience. As with other standard controls, you can configure the video presentation and event properties. Although the Pega 7 Platform supports multiple video types, use the MP4 format as a best practice.

For more information, see Adding a video to a section.

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.

Logic-based assignment routing

You can now define business logic that controls when and by whom an assignment is processed in a case. By routing assignments to a specific user or group of users, you can help ensure that cases are resolved faster.

For more information, see Logic-based assignment routing.

Grid layout supports heading level

The grid layout supports the addition of a heading level. The heading level generates semantic markup and makes the UI structurally understandable for assistive technology users. The heading level is selected in the Presentation tab of the grid layout properties.

For more information see Grid layout - Presentation tab.

Response timeout configuration for predictions

You can now set a response timeout for your predictions in Prediction Studio. By setting a response timeout, you control how Prediction Studio registers customer responses that later serve as feedback data for your predictions.

For more information, see Customizing predictions.

Make important content visible by promoting spaces

Now you can make highly relevant content more visible and more easily accessible with promoted spaces. Highlight promoted spaces on a separate tab in spaces to ensure that the most relevant content is quickly available and clearly organized. Promoted spaces are available for every user; however, only users with Super Admin privileges can promote a space.

For more information, see Granting Super Admin privileges.

SAML 2.0 single sign-on authentication in multitenant environments

Multitenant application environments can now use SAML 2.0 for single sign-on (SSO) and single logout (SLO). Application users can access any authorized SSO multitenant applications without logging in to each application individually. SAML simplifies the login and logout process for users, mitigates security risks, and reduces the implementation costs that are associated with identity management.

For more information about configuring SAML 2.0 for single sign-on, see Web single sign-on (SSO) with SAML 2.0.

Simplified support for external log management systems

Simplified support for external log management systems such as ELK (Elasticsearch, Logstash, Kibana) makes it easier to implement an external log management system. An external log management system can improve access to system log files that help diagnose and debug issues by eliminating the need to download log files from each node in the cluster.

For information about configuring ELK, see Configuring ELK for log management.

For information about using Kibana to view log files, see Pega logs in Kibana.

Customizable New Application wizard

The redesigned New Application wizard streamlines the process of creating and configuring applications, and introduces customizable application templates. When you create an application from an application template, the template defines the wizard steps that gather the information that is needed to configure your new application based on the template. After you specify the required information in the wizard, the system creates an application with the required case types, data types, access groups, and operators. You can create multiple templates, depending on the needs of your business. Sample template types are provided.

For more information, see New Application wizard.

Default quiesce strategy changed to immediate drain

The default quiesce strategy has been changed to immediate drain, which allows you to continue to access a quiescing node to perform actions until the node is removed from the load balancer, regardless of your user role. When immediate drain is enabled, and a node is in the quiesce state, the requestor state is saved after every interaction. After the node has been removed from the load balancer, the saved state can be used to restore the requestor state on a new node in the next interaction with the server.

You can change the quiesce strategy default to slow drain by modifying the value of the session/ha/quiesce/strategy setting in the prconfig.xml file to be slowDrain.