Accessibility improvements
Valid from Pega Version 7.2
Several improvements are now available that enable application accessibility. These improvements affect the wait indicator, overlays, and collapsible layouts.
The wait indicator, or throbber, announces its status to an assistive technology such as JAWS.
- When loading, the throbber announces “Loading content” or other text that can be edited in the pyThrobberLoadingText property.
- When loading is completed, the throbber announces “Loading completed” or other text that can be edited in the pyThrobberLoadingCompletedText property.
- The loading announcement is set by default to a three-second delay, which can be modified in the pyThrobberAnnouncementDelay property.
Overlays are announced by an assistive technology and overlay content can be tabbed through by using the Tab key without closing the overlay. Overlays can be closed by pressing the Esc key. This behavior applies to all overlays and modal dialog boxes that are opened as local actions and popovers that are part of the autogenerated UI.
All users, including those not using an assistive technology, can focus the expand and collapse feature of a layout by using the Tab key. The expanded or collapsed state is announced by screen readers.
Access views in one location
Valid from Pega Version 7.2
You can access the relevant views for your case type in one place. By using the Views tab in Case Designer, you can review and edit views that are used in your case life cycle. You can also configure standard views to quickly customize the fields that are displayed when a user creates, edits, or reviews a case.
For more information, see Views in a case type.
Access views in one location
Valid from Pega Version 7.2
You can access the relevant views for your case type in one place. By using the Viewstab in Case Designer, you can review and edit views that are used in your case life cycle. You can also configure standard views to quickly customize the fields that are displayed when a user creates, edits, or reviews a case.
For more information, see Views in a case type.
Date control for past and future years
Valid from Pega Version 7.2
The Date control can be configured to show only past dates, only future dates, or any date range that includes the current year. The Display range can be set to include a configurable range of previous years or next years. The number of years is relative to the user’s date.
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.
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.
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.
Connect to external REST APIs by using OAuth 2.0
Valid from Pega Version 7.2
You can now connect to external REST services that are provided by web applications, such as Twitter and Facebook, by using the OAuth 2.0 protocol client credentials grant. Your Pega 7 Platform application acts as an OAuth 2.0 client to access protected API resources. For example, you can connect to Twitter by using OAuth 2.0 to obtain a collection of tweets that match a specific query.
For more information, see Accessing protected API resources by using OAuth 2.0.