Custom DX API attributes for auto-generated controls
Valid from Pega Version 8.5
Auto-generated controls now include the option to add custom attributes for use with the Pega Digital Experience (DX) API. The attributes are part of the DX API response to the front end and you can use them to modify the run-time behavior of the UI elements in your application. For example, you can add an attribute to a field that displays a tooltip text for that field at run time. This enhancement introduces significant flexibility to application development and gives you greater control over UI components.
For more information, see Adding custom attributes for version 1 DX API to auto-generated controls.
Access PegaUnit compliance metrics from a centralized location
Valid from Pega Version 8.5
PegaUnit compliance metrics and execution rate have been added to the PegaUnit metrics tile of the Application Quality dashboard. This dashboard provides a centralized location for all PegaUnit data for a specific application.
The dashboard also supports granular PegaUnit test information for each case type and data type, similar to the process currently available on the branch quality dashboard.
For more information, see Analyzing application quality metrics.
More quality metrics on the Application Quality dashboard
Valid from Pega Version 8.1
On the Application Quality dashboard, for each case type you can now view quality metrics such as guardrail score, test coverage percentage, unit test pass rate, list of guardrail of warnings, uncovered rules, and failed Pega unit tests. These metrics are also available for rules that are used in the application but that are not a part of any case type. To access these metrics, on the Application Quality dashboard list of case types, click Find issues.
For more information, see Application Quality landing page.
Updates to the Event Strategy rule
Valid from Pega Version 7.1.9
When you design event strategies, you can use the Filter shape for basic arithmetic and text expressions. You can also specify start conditions for the tumbling and sliding windows.
Set the status of a case on stage entry
Valid from Pega Version 8.1
You can now set the status of a case when it enters a stage. By setting the status of a case on stage entry, you can communicate to stakeholders how close a stage is to resolution. For example, if a case is in the approval stage, you can set the status of the case to "Under review" when the case enters the stage.
For more information, see:
- App Studio – Changing the status of a case
- Dev Studio – Changing the status of a case
DCO Compatibility tool is deprecated
Valid from Pega Version 8.1
The DCO Compatibility tool has been deprecated. Use the Application Guardrails landing page to see the compliance score and any warnings for your application.
For more information, see Application Guardrails landing page.
Click, record, and play UI scenario tests
Valid from Pega Version 8.1
You can now record, edit, and run scenario-based UI tests in end-user portals. By using scenario-based tests, developers focus on testing an application's ability to deliver real business value instead of writing code. Developers can test autogenerated and custom controls, actions, and navigation in a specific case or in an entire portal. Test recording is available on the run-time toolbar, and tests are available on a unified landing page that provides easy access to them. For more information, see Find and fix issues by using the Accessibility Inspector.
Support for custom pre- and post-JavaScript processing for offline flow actions
Valid from Pega Version 7.1.9
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.
Improve application test coverage by running multiple sessions
Valid from Pega Version 8.1
You can improve the test coverage of your application by using a new test coverage method - Application Coverage. Multiple users can perform coverage sessions which are aggregated into a single report. By using report metrics that show the number of rules that are covered and are not covered by tests, developers can identify which areas of the application need more test coverage.
For more information, see the Test Coverage landing page.
Quality metrics now include charts with trends
Valid from Pega Version 8.1
The Application Quality landing page now contains charts that show changes in metrics over time. Landing pages for Test coverage and Unit testing also contain interactive charts with user-defined date range filters. The default date range of the charts is 2 weeks, but you can change it by using the Application: Quality Settings landing page. The historical data provided by the charts shows changes in application quality metrics over time, so that you can recognize trends and identify potential problems with application quality.
For more information, see Application Quality landing page.