Published Release Notes

Service responses in HTTP and REST connectors are no longer modified

The Pega 7.1.8 release correctly leaves form service responses for HTTP and REST connectors unmodified. Upgrade to this release if you experience a problem in Pega 7.1.7 where service responses for HTTP and REST connectors are modified when the declared type in the Content-Type header is application/x-www-form-urlencoded. In this case, the responses were modified to a base 64 representation of the bytes in the string. In Pega 7.1.8, responses of type application/x-www-form-urlencoded are mapped to the property designated on the Connector record.

Create and modify tenants only from the Tenant Management landing pages or SOAP operations

When creating or modifying tenants, do not use any of the following methods:

• Creating a new tenant definition from the Data-Admin-Tenant list
• Using the Save As feature to create a tenant from an existing tenant
• Creating a tenant from the rule form from the Action > Create menu

Although these methods might appear to work, the resulting tenants have no associated metadata and are not valid. Always use landing pages or SOAP operations to create or modify tenants.

Work attachment indexing fails with IBM SDK Java 6

Indexing of work attachments fails when you use IBM SDK Java 6 with Pega 7.1.7 through Pega 7.2. The workaround is to switch to IBM SDK Java 7 or Oracle JDK Java 1.6. You can also disable attachment indexing from the Search landing page; however, if you do this, you are not be able to search the content of attachments.

Agents not running after update of EAR-based deployment

If you update an EAR-file deployment and your update meets both of the following criteria, you must redeploy the prpc_*.ear file for your application server after you complete the update to avoid agent-related errors:

• Updating from Pega 7.1.7, Pega 7.1.8, or Pega 7.1.9
• Updating to Pega 7.1.10, 7.1.11, 7.2, or 7.2.1

If you do not redeploy the prpc_*.ear file, you will see the agent-related issues that are described in the support article Agents are not running.

For information about redeploying, see the Pega 7 Platform Update Guide for your target version of the Pega 7 Platform.

View status of custom search indexes

Custom search indexes are special purpose indexes that are created and managed outside of Pega Platform™. You can view the status of custom search indexes on the Search landing page to see whether they are complete. This information is useful for troubleshooting and can help you determine whether to rebuild the index.

For more information, see Checking search index status.

Job Scheduler and Queue Processor rules replace agents

The Job Scheduler rule and the Queue Processor rule replace agents and improve background processing. The Job Scheduler rule is used for recurring or scheduled tasks, such as sending summary emails on weekdays. This rule can be run on all nodes or on specific node types according to your customized pattern. The Queue Processor rule is used for tasks with no recurrence-based pattern. It provides scalability and capability for immediate or delayed message processing, such as submitting status changes to an external system. You can use a standard queue processor or a dedicated queue processor, depending on your processing needs.

Pega Platform™ provides a set of default queue processors and job schedulers. Corresponding agents are no longer available.

For more information about Job Scheduler and Queue Processor rules, see Job Scheduler, Replacing an agent with a Job Scheduler rule, Queue Processor, Replacing an agent with a Queue Processor rule.

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.

Security fields in JFrog Artifactory repository rule form removed

The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not functional in Pega Platform™ 7.3, 7.3.1, and 7.4. This section has been removed from the JFrog Artifactory repository rule form in Pega Platform 8.1.

Support for OAuth 2.0 authorization code grant type

Pega Platform™ now supports the OAuth 2.0 authorization code grant type, which allows Pega Platform to act as an OAuth 2.0 access token provider for native applications on mobile and other devices. By using the authorization code grant type for mobile clients, you no longer need to implement a variety of standards for various authentication providers. The authorization code grant type also supports the Proof Key for Code Exchange standard (PKCE) for securing public clients.

For more information, see Creating and configuring an OAuth 2.0 client registration.

Use client-based access control to support EU GDPR requirements

You can use client-based access control (CBAC) to satisfy the data privacy requirements of the European Union General Data Protection Regulation (GDPR) and similar regulations. By using client-based access control, you can identify the personal data of clients and automatically process requests to view, update, or remove the data in a secure manner. You can also enforce restrictions on the use of this data in application functions.

For more information, see Client-based access control.