Chart drilldown capabilities extended to dashboard widgets
Valid from Pega Version 7.3
When the chart for a report is displayed in a dashboard widget, you now can click any part of the chart to drill down and view the subset of data for that part. This enhancement provides you with an accurate view of the data that determines the report results. Previously, this capability was provided only in the Report Viewer.
Enhancements to exporting report results to Excel
Valid from Pega Version 7.3
When you export report results to Excel, the .xlsx file that the export process generates is smaller, opens faster, and no longer displays a security warning when you open it. Excel handles more of the formatting, and DateTime, Date, TimeOfDay, and Numeric properties are exported in a format that Excel recognizes. In addition, columns have sorting and filtering enabled by default.
These enhancements are enabled by default and provide improvements to performance and memory usage, especially with large data sets. You can disable this new default behavior by modifying the pyEnableExportToAdvancedExcelFormat when rule. For more information, see Disabling the default functionality for exporting reports to Excel.
Support for following users in the Pega Express and Case Manager portals
Valid from Pega Version 7.3
You can now follow users in both the Pega Express and Case Manager portals. Posts that are made by users whom you are following are displayed in your Pulse activity feed in your dashboard. In addition, an icon indicates whether followed users are online.
For more information, see the following help topics:
Enhancements to the Send Email smart shape
Valid from Pega Version 7.3
The following enhancements have been made to the Send Email smart shape:
- You can now configure the Send Email smart shape in Pega Express.
- You can use templates, such as a rejection template, in your email.
- You can use property values, which allow you to insert the value of a field in your case type, such as First Name, within the email.
- You can insert a link to the case ID in your email.
- You can more quickly configure your recipient list by using two options, instead of one, to send messages to either a list of email addresses or to fields.
- You can choose to send either all case attachments in an email, or you can send attachments of a specified attachment category or an attachment type field. You can specify multiple attachment categories and attachment type fields.
For more information, see the following help topics:
Improved data security for BIX extracts for Pega Cloud customers
Valid from Pega Version 7.3
Data security is improved for BIX extracts in the Pega Cloud. BIX extracts are now processed through the use of a HIPAA-compliant system. As a result of this improvement, the method for obtaining BIX extracts has changed. For more information, see Process for obtaining BIX extracts has changed for Pega Cloud customers.
New process for Pega Cloud customers to obtain BIX extract files
Valid from Pega Version 7.3
The process for obtaining Business Intelligence Exchange (BIX) extract and manifest files for Pega® Cloud customers has changed as a result of data security enhancements for HIPAA compliance. By default, after upgrading to Pega 7.3, you must obtain the BIX extract and manifest files from the Pega SFTP server. From within Designer Studio, you can configure the BIX extract and manifest files to be sent to a remote SFTP server by a file listener. For Pega Cloud customers who have purchased a Pega Cloud SFTP Server subscription, you can configure BIX to send the BIX extract and manifest files to the SFTP server's folders for remote SFTP client download.
For more information about obtaining files from the Pega SFTP server, see Obtaining BIX extract files from the Pega SFTP server.
For more information about having files sent to your SFTP server, see Defining SFTP-related data instances.
Multistatus case dependencies replace custom implementations
Valid from Pega Version 7.3
You can now quickly define a case dependency that supports variations of a resolved status, such as Resolved-Completed and Resolved-Rejected. Because the definition of a resolved case now includes all status values that start with the word “Resolved,” you can replace custom logic in your application with a Wait shape that you configure in a flow.
For more information about defining a case dependency, see:
- Pega Platform - Pausing a process in a case
- Pega Express - Pausing a process in a case
Cases no longer locked when followed
Valid from Pega Version 7.3
Work party properties of the type follower are no longer associated with the cases that you follow. Cases are no longer locked when you follow them, so now all users can follow a case. If you upgrade to Pega 7.3, you can run a utility to upgrade the cases that you are following so that they are no longer locked when they are followed.
For more information, see Upgrading cases and followers.
Send event notifications in Pega Platform
Valid from Pega Version 7.3
You can configure applications to notify users of case changes or other significant events that occur in an application. Use notifications to engage application users by providing key updates that might be of interest to them.
You can deliver notifications over the default web gadget and email channels or use a custom channel that you created. You can configure multiple web gadgets to display different kinds of notifications. The email channel supports notification frequency of instant, daily, or weekly.
Application users can set their own notification preferences in the run-time portals or override the set preferences for a specific case type instance.
For more information, see Sending event notifications and Management of user notification preferences.
Multiple notifications are delivered for the same Pulse post
Valid from Pega Version 7.3
When a user posts a Pulse comment, the users who subscribe to the activity feed might receive more than one notification if the posted comment triggers several notification rules.
For example, when a user posts a comment on a case that he or she follows, any response to the comment can result in the following notifications:
- Notification when a new comment is posted on the followed case (triggers the pyAddPulsePost notification definition)
- Notification when a comment is a response to the user’s original post (triggers the pyAddPulsePost notification definition)
- Notification when the user is mentioned in the comment (triggers the pyAddUserMentionedPost notification definition)