Tracer supports SOAP messages
Valid from Pega Version 7.1.5
You can now select a Tracer Settings option to display SOAP connector and services messages in Tracer, which provides users with a better understanding of SOAP connector behavior.
Actionable error message in integration wizards
Valid from Pega Version 7.1.5
Improvements have been made to the integration wizards for SOAP, SAP, and .NET that enhance the user experience by providing clearer, actionable error messages when there are problems with WSDL uploads; letting you edit the endpoint while creating or testing the integration; clarifying how the data source class layer is reused and removing confusing terms; and adding an option in Tracer to view SOAP messages generated or received by integrations.
Data page unit test case setup and cleanup
Valid from Pega Version 7.2.1
You can now use one or more data pages, data transforms, or activities to set up a clipboard page with the appropriate properties before you run a data page unit test case. You can also use activities to create any required test data, such as work or data objects.
After you run a data page unit test case, the data pages that were used to set up the test environment are automatically removed. You can now also apply additional data transforms or activities to clean up the clipboard.
For more information, see Setup and cleanup of data page unit test cases.
New assertions for data page unit test cases
Valid from Pega Version 7.2.1
You can now configure the following assertions for data page unit test cases:
- Result count assertions for page lists, page groups, value lists, and value groups
- Unordered list and ordered list assertions for page lists
The Pega 7 Platform now supports these assertions in addition to expected run-time assertions for the data page and property assertions for any property type.
For more information, see Data page unit test case assertions.
Push notification delivery to multiple devices
Valid from Pega Version 7.2.1
Push notifications sent from the Pega 7 Platform are now delivered to all devices on which a user is logged in to your custom mobile app, regardless of the device platform. You can either send push notifications from the Push Console to all users who have your application installed on their devices, or configure your application to send push notifications to indicate that an action might be required, a status update is available, or a case was approved.
Support for subflows and decision flow results in offline mobile apps
Valid from Pega Version 7.2.1
Subflows in offline-enabled mobile apps are now supported to perform additional tasks outside of the main flow. The subflow can run only on the current work item, with the subflow displaying in the main flow, in a nested subflow, or located next to an assignment. No likelihood routing is supported for subflows. It is also possible to set a flow result by using the pega.process.flow.setFlowEndStatus() JavaScript method to override the status set by a property in the subflow's end shape. The process engine also takes into account the likelihood setting if the flow result is conflicting or absent, provided the flow result is not in a subflow.
For more information, see Flow processing in offline mode.
Support for error handling API in offline mobile apps
Valid from Pega Version 7.2.1
During the processing of cases in offline-enabled mobile apps, you can use several JavaScript API methods to perform error handling. You can now determine whether an error condition results from the post-processing of a flow or a subflow. You can also set, clear, or obtain the number of error messages on a property or a page while working in offline mode, similar to when you are running a Pega 7 Platform desktop application. When you run a custom mobile app in offline mode, you can submit a form, but you cannot move the flow forward until all the errors on a page and in the page's properties are resolved.
For more information, see Error handling in offline mode and Error handling API in offline mode.
Application administrators can send push notifications
Valid from Pega Version 7.2.1
From the Push Console application, administrators can send push notifications to custom mobile app users. Notifications sent from the Push Console can contain application-wide messages, for example, when an update is available for manual download.
For more information, see Push Console landing page.
Transition effects for actions in custom mobile apps
Valid from Pega Version 7.2.1
Custom mobile apps that are developed on the Pega 7 Platform can include built-in transition effects that animate your forward or backward movement in cases that use flows. This feature adds to the look-and-feel experience of the custom mobile app.
You can also manually add a transition effect to actions that do not support built-in effects by using the Run Script action and calling the pega.desktop.setNativeTransition() JavaScript method.
For more information, see Transition effects on actions.
Execute Tests service to run all data page unit test cases
Valid from Pega Version 7.2.1
You can now use the Execute Tests service to run a set of tests at the end of build runs. An external validation engine, such as Jenkins, calls the service, which runs all data page unit test cases in your application, and returns the results in XUnit format. Use this service to validate the data in your application and to correct any issues before you deploy your application.
For more information, see Running all data page unit test cases with the Execute Tests service.