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
setting <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
Bugs fixed
The following bugs are fixed in this release.
| Issue ID | Description |
|---|---|
| SECENG-584 | Validation check for newline between certs in a cert chain causes issues with some certs in production |
| MGMT-3217 | Management API calls fail if KVMap name ends in "keys" |
| MGMT-3214 | Class conflicts can occur during JavaCallouts causing a customer's Java code to fail |
| MGMT-3185 | Error while adding orgadmins to an org |
| EDGEUI-127 | Getting insufficient permissions with new proxy editor |
| EDGEUI-119 | UI session timeout issue |
| CORESERV-671 | Seeing "No rings configured; Cannot initialize cps service" errors |
| AXAPP-2345 | Issue in listing AX custom reports for non cps customers |
| AXAPP-2302 | Daily Apigee Analytics Summary shows zero under developer adoption |
| APIRT-2750 | Traffic failures high in specific org |
| APIRT-2516 | Runtime errors in JavaScript callouts specify incorrect line numbers |
| APIRT-2508 | Exit error when calling express listen within a vault callback |
| APIRT-2336 | Gzip issue with Node.js |
| APIRT-1975 | Mask Configs not working for message.content |