Published Release Notes

Remotely start automation server jobs to perform branch operations

You can remotely start a job on your automation server, such as Jenkins, after an activity has occurred, for example, after you push a branch to a remote system of record. You can configure a continuous delivery pipeline on the job by using the branches REST service and merges REST service to detect conflicts, merge branches, and return the status of the merge. By remotely starting a job to detect conflicts and merge branches, you can more quickly deliver higher-quality software.

For more information, see the following PDN articles:

• Using branches with Pega repositories in a continuous integration and development pipeline.
• Remotely starting automation jobs to perform branch operations and run PegaUnit tests.
• Performing branch operations in a continuous integration and delivery pipeline with REST services.

Node classification

By using the node classification feature, which segregates nodes by their purpose, you can now configure one node with multiple node types. When you start a node with multiple node types, the node runs a set of agents and listeners that are associated with the specified node types. From the Node Classification landing page, you can view and configure the agents associated with node types, view listeners associated with node types, and open Agent rule forms, agent schedules, and Listener rule forms.

For more information, see Node Classification, Configuring node types for agents and listener and Node classification.

Ability to persist request data for synchronous REST Service failures

Request data can now be persisted when synchronous REST Service processing fails. To ensure that data is not lost and can be reprocessed, set the Execution Mode on the rule form to Execute synchronously (queue on error).

For more information see Service REST form - Completing the Service tab.

Portals can refresh a single page in a dynamic container

You can use a single-document dynamic container in a portal that allows you to refresh a single page in the container without reloading the entire portal, which improves performance and security. From the Properties panel, you can configure an existing dynamic container for this purpose by setting the mode to Single Document and selecting Render as a single page.

For more information, see Dynamic container settings.

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.