Support for controlling binary file upload in Pega Mobile Client
Valid from Pega Version 7.4
The Client Store API of Pega® Mobile Client has been modified so that you can suspend and resume the process of uploading binary files to the server. You can also check the state of the file uploading process. As a result, custom mobile app users can process their work items without having to wait for the synchronization process to finish.
For more information, see Pega Mobile Client API methods for controlling binary data upload and Client Store API.
Support for large binary data item storage in Pega Mobile Client and offline case attachments in Pega Platform
Valid from Pega Version 7.4
Pega® Mobile Client can now store and synchronize large binary data items and their corresponding actions from the action queue on Android and iOS devices. As a result, custom mobile app users can view, attach, and delete data files, whether the device is online or offline. For this function to work, you must enable offline case attachment support, which allows your custom mobile apps to synchronize case attachments between the Pega Platform and the mobile device.
For more information, see Enabling offline case attachments support and Client Store API.
Section preview added for templated sections in Designer Studio
Valid from Pega Version 7.4
When you create a templated section, a preview displays on the Design tab of the Section form, showing how the section will look at run time. The section preview immediately shows the results of each design change that you make as you add, move, or delete elements, resize the section, or modify the application skin. By helping you visualize the section's runtime appearance, section preview reduces rework and saves you development time.
For more information, see Section preview shows changes in real time for templated sections.
Support for additional health metrics on the Application Quality landing page
Valid from Pega Version 7.4
On the Application Quality landing page, you can monitor the health of your current application to identify areas that need improvement before deployment. The landing page provides application metrics such as the number of executable rules, the guardrail score, the number of guardrail warnings, the test coverage percentage, and the pass rate of PegaUnit tests. From this landing page, you can also view data for the entire application, for each of its cases, and for rules that are not part of any case type.
For more information, see Application Quality landing page.
View the configuration settings for Pega Platform nodes in Designer Studio
Valid from Pega Version 7.4
On the new Configuration Settings landing page, you can view a list of the configuration settings for a specific node, current or remote, or for an entire cluster. From this landing page you can diagnose settings issues, determine whether settings are loaded correctly, and review the settings' purposes. You can also download the prconfig.xml file for any node in a cluster to modify the settings. The ability to view settings for all nodes in the Cluster from a single landing page makes diagnosing configuration issues across the cluster simpler and easier than logging on to each node individually to view its system settings. For example, if a started agent does not run, you can check if agents are enabled on your system; or if some of your caches are too big, you can check the setting for the cache size. You can also determine if settings are loaded correctly, and identify discrepancies in the settings across the nodes.
For more information, see Viewing the current configuration settings of a node or the whole cluster, Downloading and viewing the prconfig.xml file for a specific node, REST APIs for viewing the configuration settings for Pega Platform.
Navigation support for test ID
Valid from Pega Version 7.4
The Navigation rule supports the addition of a test ID to each node. Test IDs support automated testing by providing a unique identifier for user interface elements. Add Test IDs to a navigation rule in the rule form configuration.
For more information, see Navigation form - Completing the Editor tab.
New PEGA0097 alert
Valid from Pega Version 7.4
In Pega Cloud, if a user attempts to establish a session and the configured maximum number of HTTP requestors on the cluster has been reached, the user is directed to a page that displays the PEGA0097 alert message. This alert helps to prevent a system from becoming overloaded.
For more information, see PEGA0097 alert.
Support for templated auto responses during email triaging of interaction cases
Valid from Pega Version 7.4
When you triage an interaction case by email, you can now select a predefined email response to provide feedback to a customer more quickly. The category that is associated with this email determines the type of responses that you can select. You can create an email response template or use an existing template.
For more information, see Defining suggested replies for the Email channel.
Submit application changes made in Pega Express to a continuous integration and delivery pipeline
Valid from Pega Version 7.4
After you make changes to your application in Pega® Express, you can submit these changes into a continuous integration and delivery pipeline that is configured in Deployment Manager. By using Pega Express to submit your application changes into staging, preproduction, and production systems, you can quickly start builds without involvement from IT.
For more information, see Starting a continuous delivery build.
Ability to run report definitions against an Elasticsearch index
Valid from Pega Version 7.4
To improve report generation performance, you can now run report definitions against Elasticsearch indexes instead of using SQL queries directly against the database. This feature is disabled by default and does not apply to reports that have features that are not supported by Elasticsearch. If a report query cannot be run against Elasticsearch indexes, Pega® Platform automatically uses an SQL query.
For information about enabling and using this feature, see Configuring a report definition to run against an Elasticsearch index.