Published Release Notes

Number and text input controls on Android devices may not display the correct keyboard

When running a Pega 7 application on a device using the Android operating system, pxNumber and pxTextInput controls may not display when using the desired on-screen keyboard. This happens when the number or text input type is set to number.

At design time, the input type is selected in the Editable Format section of the Presentation tab in the Cell Properties panel for a pxNumber or pxTextInput control. Due to a known limitation in some versions of the Android OS running on some devices, the keyboard displayed at run time may not support entry of decimal values when a Number type keyboard is specified.

To resolve this issue, use the Phone type when numbers with decimal values may be required. Using the Phone type displays a numerical phone keyboard. The Android phone keyboard includes both commas and periods so that decimals may be entered.

The Phone type selected in the Presentation tab of a Number control

Note that this issue only occurs on Android devices. It is recommended that applications for iOS continue to use type=“Number”.

Guided tours can be started automatically

You can configure a guided tour to start automatically by using the pxGuidedTourAutoStart control. You can configure the control to start a tour the first time or every time a user visits the screen where the control is used.

For more information, see Automatically start guided tours.

Faster, contextual editing of case types

Case Designer now includes a contextual property panel that helps you to quickly configure behavior in your case type. It supports case-wide properties, stage properties, and properties that are specific to an individual step.

When you click a stage or step in your case type, only relevant fields and controls are displayed, allowing you to stay focused and make decisions faster. Online help is also integrated with the property panel to give you just-in-time information.

For more information, see Contextual property panel in Case Designer.

Simplified creation of case types

A wizard is now available in the Case Type Explorer that walks you through the process of creating a case type. Helper text and default values gradually introduce you to stage-based case types to facilitate your transition from the wizard to Case Designer. To run the wizard, click Add a case type or select Add a child case type from the menu of an existing case type in the Case Type Explorer.

For more information about this wizard, see Case type wizard in the Case Type Explorer. 

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.

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.

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.