Published Release Notes

Mobile channel enhancements

The Mobile channel now supports several enhancements to Pega Infinity Mobile Client™ and provides custom mobile app options that are arranged in a more intuitive, consistent, and convenient layout. By default, custom mobile apps that you configure within the Mobile channel are generated with Pega Infinity Mobile Client. You can choose between a single webview web portal or a multi webview application layout, and configure such options as: bottom bar navigation rule, the bottom bar style, and the full screen search widget. You can also build a custom mobile app with Pega Mobile Client 7, or select a specific version of the client application.

For more information, see Configuring a custom mobile app.

Enhanced Pega Infinity Mobile Client

With the new Pega Infinity Mobile Client™ you now can build online apps that launch quickly, provide instantaneous navigation, and immediately react to user input. Pega Infinity Mobile Client uses native components for faster navigation between the screens of your custom mobile app; every tab opens in a separate webview, which accelerates switching between the tabs. Pega Infinity Mobile Client protects your sensitive information through safe and convenient single sign-on authentication and additional locking mechanisms.

For more information, see Pega Mobility and mobile clients.

Offline support for optional processes

You can now offer greater flexibility to the users of an offline-enabled custom mobile app by enabling them to start and continue optional processes while their phone is offline. When you configure a Run script action on a button within a user form, users can choose optional work, and continue it regardless of their internet connection.

For more information, see Enabling offline support for an optional flow.

Pega Mobile Preview app

You can now use Pega Mobile Preview to access multiple mobile channels and preview your Pega Platform™ application, for example, to verify that it is displayed correctly and operates as intended. Pega Mobile Preview is a native application that runs on Android and iOS devices. Compared with Pega Mobile Express, it enables switching between mobile channels and supports enhanced layout configuration options.

You can download Pega Mobile Preview from the Apple App Store or from Google Play.

For more information, see Pega Mobile Express and Pega Mobile Preview.

Changes in JSON results when checking the health of your system

Beginning with Pega Platform™ 8.2, the JSON results that are returned when you ping a Pega Platform instance have changed. JSON results now include node type and health information, including test name, status, state, and node ID. The following samples show JSON results from versions before 8.2 and as of 8.2.

JSON results for pre-Pega Platform 8.2:

{ "duration":"3954.448601", "count":"0" }

JSON results for Pega Platform 8.2 and later:

{"node_type":["WebUser"],"health":[{"last_reported_time":"2019-02-14T16:10:49.589Z","test_name":"Sample-Stream-Check","status":"success"}],"state":"healthy","node_id":"10.10.10_samplenode"}.

Support for sending emails by using Microsoft Graph

Email integration with Microsoft Office 365 now supports sending emails by using Microsoft Graph. With this enhancement, you can send email with a more secure protocol that complies with your organization’s security policy.

For more information, see Creating an email account.

App Studio enhancements further support Pega Express methodology

App Studio now includes improvements that you can use to plan your Microjourney™ in a more convenient way. The Overview workspace now includes a button to edit application details, such as name, description, and business objectives, without having to switch to Dev Studio. You can also access relevant information faster, because Case Designer displays additional details about channels, data objects, and attachments associated with a case type directly in a properties pane. For improved management of your features, feature categories are now available in the application inventory so that you can clearly communicate to your development team what type of features need implementation.

For more information, see:

• Editing application details in App Studio 
• Associating personas with channels 
• Adding features to application inventory 
• Creating a Microjourney for customer success

Conversation flow and smart shapes for the Digital Messaging chatbots

When creating Pega Intelligent Virtual Assistant™ (IVA) for Digital Messaging, chatbot developers can now use new conversation smart shapes in a dedicated flow, making the design process simpler, more robust, and intuitive. With the new smart shapes, the chatbot displays text messages or asks questions to users in one of several ways. In addition, developers do not have to create additional rules, switch tabs, or perform manual validation. You can associate the conversation flow that you create for your IVA with a business case, use the flow on its own, or reuse it in another conversation flow, improving the overall chatbot design process.

For more information, see Adding a stand-alone conversation process for a conversational channel, Adding a case type conversation process for a conversational channel, Editing the conversation smart shapes and Flow shapes.

Support for REST connectors to route network traffic via proxy

To easily route network traffic, you can now configure proxy details for individual REST connectors. This enhancement allows you to manage your proxy settings so that you can securely access online resources that lie beyond your proxy servers.

For more information, see Configuring a REST connector.

Connect-HTTP support discontinued

Pega Platform™ no longer supports Connect-HTTP rules. HTTP connectors were used to start HTTP request/response interactions between Pega Platform and external systems identified by a Connect HTTP rule (Rule-Connect-HTTP rule type).

After an upgrade to Pega Platform 8.6 and later, you can still use and modify existing HTTP connectors, but you cannot create new ones. As a best practice, use REST connectors instead, which offer more capabilities and have better support from development teams.

For more information, see Connect REST rules.