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.
Support for Amazon Web Services Direct Connect
Valid from Pega Version Pega Cloud
Pega® Cloud supports the Amazon Web Services (AWS) Direct Connect service between your Pega Cloud virtual private cloud (VPC) and your physical infrastructure within a geographical region without need for a virtual private network (VPN). Use this service to connect to:
- A data center provider that is located with AWS within the same geographical region.
- A multiprotocol label switching (MPLS) network or other type of wide area network (WAN).
For more information, see Configuring Amazon Web Services (AWS) Direct Connect in your Pega Cloud virtual private cloud.
This functionality is available as of QII 2016.
VPN backup for Amazon Web Services Direct Connect
Valid from Pega Version Pega Cloud
On Pega® Cloud, you can configure redundancy for the Amazon Web Services Direct Connect service in your network. Pega Cloud supports the following options for redundancy:
- An additional AWS Direct Connect service (redundant direct connection)
- Failover to customer VPN
For more information, see Pega Cloud VPN service and Configuring Amazon Web Services (AWS) Direct Connect in your Pega Cloud virtual private cloud.
This functionality is available as of QII 2016.
Virtual private cloud (VPC) peering connection support
Valid from Pega Version Pega Cloud
You can now use a virtual private cloud (VPC) peering connection to access your systems of record or transfer data between your Pega® Cloud VPC and your Amazon VPC. VPC peering is a virtual connection within the Amazon Web Services (AWS) architecture that enables one-to-one networking connections between VPCs within the same region.
For more information, see Requesting a virtual private cloud (VPC) peering connection.
This functionality is available as of Q2 2017.
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.