Published Release Notes

Multistatus case dependencies replace custom implementations

You can now quickly define a case dependency that supports variations of a resolved status, such as Resolved-Completed and Resolved-Rejected. Because the definition of a resolved case now includes all status values that start with the word “Resolved,” you can replace custom logic in your application with a Wait shape that you configure in a flow.

For more information about defining a case dependency, see:

• Pega Platform - Pausing a process in a case
• Pega Express - Pausing a process in a case

Enhancements to branches

Several enhancements to branches make it possible for you to now do the following tasks.

• You can see all branches in your application and built-on applications by clicking App > Branches.
• You can view all the rules in a branch in addition to quality statistics, such as the number of merge conflicts and guardrail warnings.
• You can run PegaUnit tests that are configured on rules in a branch.
• You can import branches from and push branches to a repository.
• You can create reviews of branch contents.

For more information, see Enhanced features for branches.

Create pluggable web storage components for case and Pulse attachments

You can now implement and post your own pluggable web storage components for use with case and Pulse attachments. These web components can be plugged in to Pega^® Platform without the need to make changes to Pega Platform itself. The ability to create a pluggable web storage component is useful when you want to use a web storage provider that does not have an existing pluggable web storage component.

For more information, see Guidelines for creating pluggable components for storing and sourcing case and Pulse attachments.

Case types and data types open in a landing page

In Pega^® Express, Case Designer and the Data Designer now open in a landing page rather than a modal dialog. This enhancement improves the user experience for creating and updating case types and data types.

Support for Couchbase Server NoSQL database

Pega^® Platform can now read data from and write data to a Couchbase Server database. Couchbase is a NoSQL database that you can use when a NoSQL database better meets your scalability and processing requirements.

For a list of supported and unsupported features, see Couchbase Server support.

Deprecated support for Microsoft ActiveX controls

Beginning with Pega Platform 7.3, Microsoft ActiveX controls are no longer supported in any version of the Pega Platform, and technical support for ActiveX is limited. It is recommended that you use HTML-based, cross-browser solutions for improved performance and greater security.

For more information, see Deprecation of ActiveX controls in Pega Platform.

Tab groups are deprecated

Beginning with Pega 7.3, tab groups have been replaced with layout groups, which offer better performance and flexibility. Tab groups are based on the Yahoo User Interface (YUI) library, which is no longer supported on the Pega 7 Platform.

User interface rule forms now use layout groups instead of tab groups to place layouts in forms.

For more information, see Adding a Layout Group.

Layout groups support icons and titles in headers

You can now include icons or cells to enhance the design of layout group headers. On the properties panel, select Include icon with title under Container settings to add icons and titles in the layout headers. Also, the layout group control can now refresh the content of a dynamic layout if the layout is active.

For more information, see Adding a Layout Group.

Edit sections in Pega Express at run time

You can enable editing of sections that were created by a template. Run-time editing allows Pega Express business users to identify and edit sections that contain content. You mark sections as editable by selecting the Allow section to be edited at runtime check box on the Settings tab of the section. For more information, see Run-time editing of sections in Pega Express.

Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3

If you used node classification in Pega^® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type.

• UniversalNode becomes Universal
• WebUserNode becomes WebUser
• BackgroundProcessingNode becomes BackgroundProcessing
• BIXNode becomes BIX
• SearchNode becomes Search

If you created agents in Pega 7.2.2, agent schedules are also automatically updated with a new name during the upgrade. For more information, see Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade and the appropriate Deployment Guide.