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 REST services and APIs by using OAuth 2.0
Valid from Pega Version 7.2
You can now allow external client applications to access REST services on your behalf by using the OAuth 2.0 protocol client credentials grant. The Pega 7 Platform acts as an OAuth 2.0 provider to grant trusted applications access to functions in Pega 7 Platform applications. Additionally, you can provide access to the Pega API by using OAuth 2.0.
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.
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.
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.
Data modeling in context for case types
Valid from Pega Version 7.2
You can access the part of your data model that is relevant to your context. By using the Data model tab in Case Designer, you can quickly add, remove, or configure the fields that are used by an individual case type.
For more information, see Data models for case types.
PegaWAI ruleset deprecated in 8.5
Valid from Pega Version 8.5
Accessibility functions that were contained in the PegaWAI ruleset are now integrated into the main Pega Platform™. Consequently, the user interface in your applications now features accessibility functions out of the box, so you no longer need to use the PegaWAI ruleset to ensure accessible behavior in your application.
For more information, see Building an accessible UI.
Information Mashup section for OAuth 2.0 provider authorization
Valid from Pega Version 7.2
You can now add an Information Mashup (pxInformationMashup) section to a layout, a region, another section, or a cell in a layout to delegate access to OAuth 2.0-protected resources. Configure the section with an OAuth 2.0 authentication profile, mashup section, and authorization section to connect to an external application at run time. For example, users can log on to Facebook from the Pega 7 Platform by using this section and access photographs in their Facebook account.
For more information, see Access protected API resources by using OAuth 2.0.
Authorization code grant for OAuth 2.0 providers
Valid from Pega Version 7.2
You can now connect to OAuth 2.0-protected APIs by selecting the authorization code grant type on the OAuth 2.0 Provider rule form. Enter the authorization code, access token, and revoke token endpoints as indicated by your OAuth 2.0 provider, for example, Box or Facebook.
For more information, see Access protected API resources by using OAuth 2.0.
Updates to the Authentication Profile rule form
Valid from Pega Version 7.2
You can now create OAuth 2.0 authentication profiles by using the enhanced rule form. For this profile type, you can select an OAuth 2.0 Provider data instance, a grant type, and the client information that you obtained from your OAuth 2.0 provider, such as Box or Facebook. You can also revoke issued access tokens on this rule form.
For more information, see Access protected API resources by using OAuth 2.0.