Published Release Notes

The System Management Application is supported only on Microsoft Internet Explorer

Microsoft Internet Explorer (IE) is required for the System Management Application (SMA). No other browser is supported.

Enhanced options for resolution stages

When configuring a stage that resolves cases in Case Designer, you can now:

• Create a new resolution status.
• Select the status that is assigned to a case when it completes the last step in the stage.
• Instruct your application to close all open assignments when a case is resolved.

At run time, the audit trail of a case includes entries that capture the time that the case was resolved and open assignments were closed. To access the configuration options for a resolution stage, click Resolve the case on the General tab of the contextual property panel in Case Designer.

For more information about configuring a resolution stage, see Options for a stage that resolves cases.

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.

Enhanced interoperability with enterprise content management products

The Content Management Interoperability service (CMIS) capabilities of the Pega 7 platform now provide enhanced interoperability with enterprise content management products. This improvement uses modern web services components that require a Pega platform running Java 7 or higher when CMIS connectivity through SOAP web services are utilized.

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.

Deprecated rule types

The following rule types have been deprecated as of the Pega 7.1.8 release:

• Form
• Hierarchy
• Service COM
• Service BPEL
• Connect BPEL
• Parse Transform
• Parse Transform Collection
• Parse Infer

For more information, including suggested alternate rule types, see the help topic Deprecated features.

The Create Build button appears grayed out when configuring and building a mobile application

When you attempt to configure and build your Android or iOS mobile application from the Mobile tab, the Create build button might appear dimmed. This issue occurs if any of the access roles in the access group were cloned from the PegaRULES:SysAdm4 access role.

Refer to Troubleshooting Pega Mobile Client to learn how to fix this issue in your application.

Resolved Issues for This Release

For details on the Resolved Issues for this release, visit the Resolved Issues page.

Decision Data Store data sets can be used only on DNodes

Data flows that contain Decision Data Store data sets as the primary or secondary source must be created and executed only on DNodes.

Data flows are not restarted automatically after application server restart

When you restart the application server or the Pega 7 server, you stop the execution of your data flows. The interrupted batch and real-time runs are marked as Failed. 

Recommendation:

• Go to the Designer Studio > Decisioning > Decisions > Data Flows > Batch processing tab and start the failed batch runs.

• Go to the Designer Studio > Decisioning > Decisions > Data Flows > Real-time processing tab and activate the failed real-time runs.