Automatically process cases with SharePoint
Valid from Pega Version 7.3
You can now use Microsoft SharePoint Online to store and source case and Pulse attachments and to store and source attachments during automated case processing. Users only have to provide authentication and authorization details the first time they access SharePoint Online or when the trust has expired. The authentication profile must be OAuth 2.0 with a grant type of authorization code. The SharePoint Online component can be downloaded from Pega Exchange. For more information, see Downloading and configuring pluggable content management components.
Ability to set default values when importing data
Valid from Pega Version 7.3
You can now set default values for data that you import for a data type from a .csv file. By setting defaults, you can ensure that even when the .csv file data is incomplete, all of the data is imported. In addition, you can set default values for custom fields that do not have a matching source column in the .csv file. This feature is available for the Add and update and Add only import options. For mapped fields, the default value is used for new records if the source field is blank, and for existing records if both the source and target fields are blank. For custom fields, the default value is used for new records if a default value is provided, and for existing records only if the target field is blank.
For more information, see Importing data for a data type.
Ability to persist request data for synchronous REST Service failures
Valid from Pega Version 7.3
Request data can now be persisted when synchronous REST Service processing fails. To ensure that data is not lost and can be reprocessed, set the Execution Mode on the rule form to Execute synchronously (queue on error).
For more information see Service REST form - Completing the Service tab.
Create pluggable web storage components for case and Pulse attachments
Valid from Pega Version 7.3
You can now implement and post your own pluggable web storage components for use with case and Pulse attachments. These web components can be plugged in to Pega® Platform without the need to make changes to Pega Platform itself. The ability to create a pluggable web storage component is useful when you want to use a web storage provider that does not have an existing pluggable web storage component.
For more information, see Guidelines for creating pluggable components for storing and sourcing case and Pulse attachments.
Data Import wizard supports all Microsoft Excel default formats
Valid from Pega Version 7.3
The Data Import wizard for data types now supports all Microsoft Excel default date formats. Dates are easier to handle and you are alerted before data is imported if the date format is not supported.
For more information about supported date and time formats, see Date and time formats supported by the Data Import wizard for data types.
Property-level security for full-text search
Valid from Pega Version 7.3
Property-level security has been added to full-text search so that you can limit access to sensitive data. From the Search landing page, you can specify whether to include properties with access control policies in search results. In addition, for custom search, you can select which properties to include in full-text search by selecting options on the Search landing page and Custom Search properties instance.
For more information, see Specifying custom search properties and Excluding properties with access control policies from search results.
Fallback activity for Service REST and SOAP
Valid from Pega Version 7.3
You can now configure a fallback response activity for a time-out for Service REST and SOAP. Using a fallback response activity makes it easier to meet a service-level agreement (SLA) by providing a logical response in a timely manner. For example, the fallback activity can display a default offer to an ATM customer instead of an offer that is based on that particular customer's data.
For details about configuring the fallback response activity, see Service REST form - Completing the Service tab and Service SOAP form - Completing the Service tab.
New service for generating OAuth 2.0 client credentials
Valid from Pega Version 7.3
Pega® Platform now includes the oauthclients service package that provides a REST service for generating OAuth 2.0 client credentials. By using the client registration service, you can dynamically register OAuth 2.0 clients. The new service is secured by an existing OAuth service. Access tokens that are issued by the existing OAuth service are accepted as initial access tokens by the new service.
For more information, see OAuth 2.0 Client Registration data instances.
Enhanced security of Robotic Desktop Automation requests
Valid from Pega Version 7.3
Security enhancements have been introduced in the communication (data synchronization or pulling data) between your application that uses robotic desktop automation functionality and Pega® Platform. These applications (web, desktop, and legacy) communicate with Pega Platform through connectors. No additional configuration is necessary.
For more information, see Robotic automation.
Record Editor and data import enhancements
Valid from Pega Version 7.3
The Record Editor and Import wizard for data types have been enhanced to make the import process faster and easier to use. You can now perform the following tasks.
- Configure the Record Editor to use full-text search, which makes searching faster.
- Configure the location of the data import error file. For example, you can set the location to a shared location so that users can access the file from any node in a multinode system.
- Pass the keys of the records that were added, updated, or matched directly to custom postprocessing without additional database I/O.
- Search and filter records and export only the results instead of all records.
- Stop an import that is in progress.