View PegaUnit test reports
Valid from Pega Version 7.3.1
The Reports tab on the Automated Testing landing page contains tables and charts that display the percentage of rules on which PegaUnit test cases are configured, and the results of PegaUnit test execution. By looking at the data on this tab, you can see which tests failed and investigate them.
For more information, see Viewing PegaUnit reports.
Attach Content control enhancements
Valid from Pega Version 7.3.1
You can now use the Attach Content control in Pega® Platform to configure compression options that limit the size of files created on a mobile device. For example, you can choose from predefined settings to limit video duration or image size. These settings apply when the user records a new video or takes a new photo, but they do not apply to prerecorded media.
Also, when attaching content to a custom mobile app, users can now select any type of file from any source that is available in the device's native file picker component.
For more information, see Configuring file size options for the Attach content control.
Requestor pools management in Designer Studio
Valid from Pega Version 7.3.1
On the new Requestor Pools landing page, you can view and manage requestor pools across the cluster, including on the current node and remote nodes. By using this landing page, you can tune the requestor pools to improve the performance of services. You can clear the requestor pool for a service package and view the requestor pool basic metrics and configured thresholds.
For more information, see Requestor pools management, Clearing a requestor pool, Viewing details for a requestor pool, Tuning a requestor pool configuration.
Like and bookmark Pulse messages
Valid from Pega Version 7.3.1
You can now like messages that are posted to Pulse and view the number of likes for each message. You can also bookmark the messages that you want to view in your activity feed.
For information about Pulse enhancements, see:
- Pega Express 7.3.1 – Communicating with Pulse
- Pega Platform 7.3.1 – Pulse enhancements for social collaboration
Real-time updates in Pulse
Valid from Pega Version 7.3.1
You can now view real-time updates of messages in Pulse. If a user posts a comment on a Pulse conversation while you are viewing the conversation, you receive a notification in real time, which you can click to refresh the conversation and see the comment.
For information about Pulse enhancements, see:
- Pega Express 7.3.1 – Communicating with Pulse
- Pega Platform 7.3.1 – Pulse enhancements for social collaboration
Monitor application health on the Application Quality landing page
Valid from Pega Version 7.3.1
On the Application Quality landing page, you can view various quality-related data in one place so that you can monitor the quality of your application and correct any issues. The Application Quality landing page contains a summary of guardrails compliance, PegaUnit test coverage, and results of PegaUnit tests.
For more information, see Application Quality landing page.
Enhanced activity feed for Pulse displays messages
Valid from Pega Version 7.3.1
The activity feed for Pulse has been enhanced to display replies to messages that you have posted, messages on cases that you are following, messages in which you are referenced, messages posted on your user profile, messages by users that you are following, and messages that you have bookmarked. You can filter the activity feed to display the messages that you want to view.
For information about Pulse enhancements, see:
- Pega Express 7.3.1 – Communicating with Pulse
- Pega Platform 7.3.1 – Pulse enhancements for social collaboration
Service REST monitoring
Valid from Pega Version 7.3.1
You can now monitor response and request data for REST services and view the results in Pega® Platform. The ability to monitor REST services is useful for debugging your application during development, for example, when a request fails. It is not recommended that you monitor REST services in production environments because monitoring might affect performance and depending on the number of incoming service requests, there is a chance that over a period of time, the invocation history might get large enough so that you run out of database space. You can configure monitoring globally for all of your REST services by using the service/EnableglobalMonitoring Dynamic System Setting with owning ruleset Pega-IntegrationEngine, or by using the service package and service rule forms.
For more information, see Service REST monitoring.