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.
Log file description in web.xml incorrect after upgrade to Apache Log4j 2
Valid from Pega Version 7.3
As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, it is recommended that you update the log file description in the web.xml file from location of prlogging.xml file to location of prlog4j2.xml file. The description indicates which log file is in use. Updating the description avoids confusion about which log file is current. Change the description as shown in the following example.
<resource-ref id="ResourceRef_5">
<description>location of prlog4j2.xml file</description>
<res-ref-name>url/pegarules.logging.configuration</res-ref-name>
<res-type>java.net.URL</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
Experimental high-speed data page support
Valid from Pega Version 7.3
An experimental implementation of high-speed, read-only data pages is available. This implementation is useful when data pages are used to hold static data that is used repeatedly. You can enable this feature for a specific read-only data page from the Load Management tab of the data page rule form by clicking Enable high-performance read-only data page. This feature does not support full clipboard page functionality; use with caution.
The following functionality is supported:
- Basic page and property access (read and write properties) for all normal data types
- Hierarchical data page structure (pages within pages)
- Dictionary validation mode
- Read-only data pages
The following functionality is not supported:
- Declarative rules
- Page messages
- Complex property references
- Saving pages to a database
- API access to the data page