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.
Multistatus case dependencies replace custom implementations
Valid from Pega Version 7.3
You can now quickly define a case dependency that supports variations of a resolved status, such as Resolved-Completed and Resolved-Rejected. Because the definition of a resolved case now includes all status values that start with the word “Resolved,” you can replace custom logic in your application with a Wait shape that you configure in a flow.
For more information about defining a case dependency, see:
- Pega Platform - Pausing a process in a case
- Pega Express - Pausing a process in a case
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.
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.
Cases no longer locked when followed
Valid from Pega Version 7.3
Work party properties of the type follower are no longer associated with the cases that you follow. Cases are no longer locked when you follow them, so now all users can follow a case. If you upgrade to Pega 7.3, you can run a utility to upgrade the cases that you are following so that they are no longer locked when they are followed.
For more information, see Upgrading cases and followers.
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.
New Java API improves JSON serialization
Valid from Pega Version 7.3
By using a Java API, you can serialize a Page or Property clipboard object to a JSON string for faster JSON serialization. You can also create a map between API responses and an application's internal data model that improves integration performance and maintainability.
For more information, see Using the mapping API for high-performance JSON serialization and Using the mapping API for high-performance JSON deserialization.