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.
SystemCleaner agent is split into node-level and cluster-level agents
Valid from Pega Version 7.3
The Pega-RULES:SystemCleaner agent has been split into node-level and cluster-level agents to avoid database performance issues. The new node-level agent, Pega-RulesEngine:NodeCleaner, runs on all the nodes in the cluster, while the new cluster-level agent, Pega-RulesEngine:ClusterAndDBCleaner, runs on only one node in the cluster. If you customized the agent schedules of the Pega-RULES:SystemCleaner agent, you must manually update the agent schedules of the new agents because customized schedules are not retained.
For more information, see Agent schedule data instances – Completing the Schedule tab.
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.
Greater cluster stability with client-server clustering topology
Valid from Pega Version 7.3
You can now deploy Pega® Platform in the new client-server clustering topology that uses Apache Ignite, which increases stability in large clusters and provides independent scalability for both servers and clients. This technology separates the client nodes, which are responsible for Pega Platform processes, from the server nodes, which are responsible for cluster communication and distributed features. If your production environment consists of more than five nodes in the cluster, it is recommended that you switch to the new client-server topology.
For more information, see Apache Ignite client-server clustering topology and the appropriate Deployment Guide.
Create pre-import and post-import steps
Valid from Pega Version 7.3
To take specific actions based on archive metadata, add pre-import and post-import action steps to collections. For example, you can configure a pre-import activity to automatically verify that an archive meets certain criteria before you import the archive. If the archive does not meet the criteria, Pega® Platform does not import the archive.
For more information, see Pre-import and post-import collections.
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.
Rollover policy for log files
Valid from Pega Version 7.3
The rollover policy for log files is now based on time (daily) and file size (maximum file size is 250 MB). Log files are rolled over daily or when the maximum file size is reached. Current (not rolled over) log files do not have a time stamp. The time stamp is added when the log file is rolled over. In addition, the log file name for the current log file does not include the date. You can add the date to the current log file; however, the log file will not be rolled over. In addition, the web.temdir variable for setting the log file location is no longer supported; use the pega.logdir variable instead.
For more information, see Pega Platform logging with the Log4j 2 logging service.
Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade
Valid from Pega Version 7.3
If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type. Agent schedules for standard Pega Platform agents are deleted and re-created with the new node type name, but any customization that you made in Pega 7.2.2 is not saved. You must manually update the agent schedules for standard Pega Platform agents in Pega 7.3.
For more information, see Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3 and the appropriate Deployment Guide.
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.
Push notifications and Oracle WebLogic Server 10.3.6
Valid from Pega Version 7.2.2
Pega® Platform push notifications can use WebSockets and long polling. However, for WebLogic Server 10.3.6, the push notifications feature does not work. To disable the feature, contact Pegasystems Global Customer Support.