Published Release Notes

Support for custom pre- and post-JavaScript processing for offline flow actions

Developers of an offline-enabled mobile app can execute basic business logic before and after a flow action is rendered by adding their own JavaScript code into a custom user scripts bundle. Its functions must be called within a try/catch clause. The JavaScript code, to be executed before a flow action is rendered, is always called afterClientCache is called and before DisplayHarness is called.

Conditional online and offline map display

The way an Address Map control behaves in a offline-enabled mobile app has changed. When a mobile app is online, a live Google map is loaded as expected. If the mobile app goes offline, a predefined image of a map is loaded instead.

Troubleshooting Pega Mobile Client on the login screen

An offline mobile developer can now troubleshoot issues that are not related to incorrect credentials when signing in to the Pega Mobile Client app. On the app login screen, an alert box displays where the user can click a link to examine current log files to troubleshoot the issue. The contents of the displayed log file can be filtered.

For more information, see Troubleshooting Pega Mobile Client.

New Pega Mobile Client debugging options

The Mobile tab on the Application form contains two new options: a check box for enabling debugging in the Pega Mobile Client app, and a drop-down field for setting the log level to one of the following levels: Silent, Error, Warning, Info, or Debug.

For more information, see Mobile settings reference.

Ability to view a PDF file while offline

Users of offline-enabled mobile apps can now tap a button to view a PDF file, regardless of whether the user is online or offline. The associated button, link, or icon must have a Run Script action defined that calls the pega.ui.pdf.view() function with two parameters: applicationName and pdfName. The PDF file itself must be uploaded to a Rule-File-Binary rule.

For more information, see How to set up viewing of PDF file while offline.

Building a Pega Mobile Client with custom modules

When you build a Pega Mobile Client mobile app using the Pega 7 Platform, you can now include Android or iOS custom modules. The custom modules must be included in the assets.zip file that contains the Pega Mobile Client branding and customization details.

For more information, see Building a mobile web app into a hybrid mobile app.

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.

Ability to forward emails in triage cases

When working on customer emails in the Email Manager or Case Manager portal, customer service representatives (CSRs) can now forward emails to additional stakeholders, for example, third-party vendors or sellers. As a result, CSRs that work with Pega Email Bot™ save time, improve responsiveness to customer inquiries, and make email triaging more efficient. The email bot keeps each forwarded email conversation in a separate email thread from the customer conversation, making the system more consistent and secure.

For more information, see Communicate with stakeholders on a customer query by forwarding emails and Forwarding emails to other stakeholders for an email bot.

Outbound email templates for email bots

Pega Email Bot™ now provides built-in templates for outbound email and an option to create your own, custom templates. You can use this feature to standardize branding for your applications and the company through your communication channels. For example, customer service representatives (CSRs), who use the Email Manager or Case Manager portals, can apply these templates to strengthen your brand's presence in every email that they send or that the email bot automatically sends as an acknowledgment for a user email.

You select an outbound email template when you configure the Email channel. The system provides you with three built-in outbound email templates that you can select or modify to fit the requirements of your organization.

For more information, see Creating an Email channel and Creating outbound email templates.

Tracer file size limit to prevent disk usage issues

The maximum size of files with event details that Tracer generates is now 10 GB to avoid excessive disk usage and performance issues. Tracer applies the size limit at the node-level, so every node that runs in your system can use up to 10 GB of disk space to create an output file with event details. As a result, you can monitor the health of your system and deliver issue-free applications without experiencing disk space problems.

For more information, see:

• Avoid performance issues when monitoring applications with size limit for Tracer files (8.6)
• Tracer disk usage FAQ