Published Release Notes

Data pages can source information from a robotic process automation

When you use robotic process automation (RPA), you can now configure data pages to source information from robotic automations so that you can connect your Pega® Platform application to legacy applications in your enterprise. By using automations to retrieve data and save it to a data page, you can use data virtualization to encapsulate your Pega Platform data model from the physical interface of a legacy system against which the automation is running.

For more information, see Obtaining information from robotic automations.

CRM core data types included in Pega Platform

Customer Relationship Management (CRM) core data types are now included with Pega^® Platform, making it easier to bring your data into your Pega application. You can either import your data into the data tables for the CRM data types or use integration to communicate with your own system of record. The database tables for these data types are non-Pega formatted, which gives you better performance and more control over your data.

For information about the database tables, see CRM data types in Pega Platform.

PegaDATA connection settings now required in the prconfig.xml file

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.

Node classification replaces NodeID-based configuration

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.

Pega Cloud Services File Storage service

Pega Cloud Services introduces Pega Cloud Services File Storage, a service that is fully integrated with the Pega Platform to support your Pega applications. New subscriptions and upgrades to the latest Pega Platform version make this the default storage repository.

For more information see Pega Cloud Services File Storage.

Pega Cloud Services introduced this new service as of QI 2018.

Support for Java 8

Improve application test coverage by running multiple sessions

You can improve the test coverage of your application by using a new test coverage method - Application Coverage. Multiple users can perform coverage sessions which are aggregated into a single report. By using report metrics that show the number of rules that are covered and are not covered by tests, developers can identify which areas of the application need more test coverage.

For more information, see the Test Coverage landing page.

Use fast processing option does not work

The Use fast processing option on Connect REST and Service REST rule forms does not work unless you obtain the HFix-43000 hotfix from Global Customer Service.

Use the following data model guidelines when using fast processing:

• The JSON property names and the clipboard property names must match.
• The JSON tree structure and the clipboard tree structure must be similar.
• The scalar arrays in JSON must be mapped to the clipboard as page lists.
• Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.

​In addition, page groups, value groups, and Java objects are not supported by fast processing.

Applications not working as expected when using fast processing for Connect REST and Service REST integration

In Pega^® Platform 7.3.1, the Use fast processing option on Connect REST and Service REST rule forms did not work. The functionality has been fixed for Pega 7.4; however, some data model guidelines must be followed. If you use this option in Pega 7.3.1, and you did not follow the guidelines, your application might not work as expected after upgrading. Use the following data model guidelines when using fast processing:

• The JSON property names and the clipboard property names must match.
• The JSON tree structure and the clipboard tree structure must be similar.
• The scalar arrays in JSON must be mapped to the clipboard as page lists.
• Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.

In addition, page groups, value groups, and Java objects are not supported by fast processing.

REST APIs added for management of agents and requestors

You can use new REST APIs to download a module version report or manage requestors and agents in Pega Platform™. For example, you can use a requestor REST API to end a requestor process, and you can use an agent REST API to start or stop an agent. These APIs allow external systems to report and manage Pega resources.

For more information, see Pega API for Pega Platform and Pega API.