You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Tuesday, April 28, 2015, we released a new cloud version of Apigee Edge.
If you have questions, go to Apigee Customer Support.
For a list of all Apigee Edge release notes, see Apigee Release Notes.
When generating analytics reports with the management UI or API, data older than six months from the current date is not accessible by default. If you want to access data older than six months, contact Apigee Support.
The following bugs are fixed in this release.
|Remove FaultRules element from default attachment template
The FaultRules element, which is not used in policies or API proxy steps, is no longer automatically added when you create API proxies or add policies.
|Fetch WSDL returns failure: "Fetch WSDL Error: Error processing WSDL."
|UI error while adding developer
|Get an OAuth 2.0 authorization code API returns wrong status
|Unintuitive roles in management UI
If a user does not have permission to create or edit a Transaction Recording Policy, the UI buttons to create and edit a Transaction Recording Policy are now disabled.
|Fetch WSDL error while importing WSDL file with .xml extension
|Cannot add user with email address which has a TLD of .acn
|SmartDocs: Description of body type parameter in Swagger definition not shown in doc UI
|SSL handshake failures due to "unrecognized_name"
|Cache performance statistics incorrect
This release has the following known issues.
|Inconsistent balance and usage for developers with multiple active rate
In monetization, if a developer is active on more than one rate plan that has per-API call charges, then monetary balance usage may sometimes be inconsistent.