You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Thursday, March 31, 2016, we released a new version of Apigee Edge for Public Cloud.
New features and enhancements
Following are the new features and enhancements in this release.
Fixed-length prefix for syslog message logging
The Message Logging policy has a new
<FormatMessage> element in
the Syslog configuration. By
<FormatMessage>true</FormatMessage>, Syslog messages
begin with a fixed number of characters, which lets you filter out Apigee-inserted data. For more
information, see Message
Logging policy. (APIRT-1398)
JSON payloads in Assign Message and Raise Fault policies
The following bugs are fixed in this release.
|Validation check for newline between certs in a cert chain causes issues with some certs in production
|Management API calls fail if KVMap name ends in "keys"
|Class conflicts can occur during JavaCallouts causing a customer's Java code to fail
|Error while adding orgadmins to an org
|Getting insufficient permissions with new proxy editor
|UI session timeout issue
|Seeing "No rings configured; Cannot initialize cps service" errors
|Issue in listing AX custom reports for non cps customers
|Daily Apigee Analytics Summary shows zero under developer adoption
|Traffic failures high in specific org
|Exit error when calling express listen within a vault callback
|Gzip issue with Node.js
|Mask Configs not working for message.content