On Tuesday, June 2, 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.
New features and enhancements
Following are the new features and enhancements in this release.
SmartDocs general availability
SmartDocs is graduating from beta to general availability. Updates and new features include:
- Support for Swagger 2.0, including import by file or URL, including support for custom-named security objects.
- Visual design improvements in the templates that generate SmartDocs.
- Usability and workflow enhancements in the Developer Portal, available through the Content > SmartDocs menu in Drupal.
- What has been known as "Custom Token" authentication is now called "API Key".
- Authentication "security" objects defined at the revision level.
- Configuration of client authentication at the template level. New revisions no longer reset any preconfigured SmartDocs client credentials.
For more feature descriptions, see this blog post.
For SmartDocs documentation, see Using SmartDocs to document APIs.
New API proxy editor beta
A new beta version of the API proxy editor is available. To access, click the "Access the Beta Version" link when editing an existing API proxy. You can switch back and forth between the "classic" and "beta" editors.
New OAuthV2 policy
The new DeleteOAuthV2Info policy lets you delete authorization codes and access tokens. For more information, see Delete OAuthV2 Info policy.
New entities in Access Entity policy
The Access Entity policy provides access to the following new entities: consumerkey-scopes, authorizationcode, requesttoken, and verifier. For more information, see Access Entity policy.
Showing SSL certificates that are near expiration
The SSL Certificates page in the management UI (Admin > SSL Certificates) indicates when SSL certificates are expiring within 10, 15, 30, or 90 days, depending on your selection in the new expiration drop-down field.
Developer app name displayed in the management UI
Developer apps in Edge have both an internal Name that doesn't change and a Display Name that you can change. On a Developer App page in the management UI (Publish > Developer Apps > app name), the app internal "Name" is displayed along with the "Display Name", making it easier to visually identify apps by their internal names for troubleshooting and API management.
Classic version of custom reports being removed from the management UI
The optional classic version of custom analytics reports is no longer available in the management UI.
SmartDocs upgrade process
If you've already been using SmartDocs during the beta period, new features and capabilities in the general availability version require that you upgrade SmartDocs in your developer portal.
Any SmartDocs pages that have already been published in your developer portal will continue to work, but you must follow the update process before editing or publishing any changes to existing or new pages.
Keep in mind that while you can render and publish SmartDocs inside your developer portal, SmartDocs are generated from the API model that lives within Apigee's Edge API Management Services. Any changes you make to an API model in Edge will be the same across all your Pantheon environments (similar to how developers exist across Pantheon environments).
To upgrade from SmartDocs beta to general availability
- Update and test the 15.05.27 release in your dev or test environments on Pantheon.
- Create a new model to replace any existing API model you have been using.
- If you have been importing Swagger or WADL documents, import them again into a new revision.
- If you have been maintaining your API model via the SmartDocs module, export as SmartDocs JSON and import into your new model using file attachment.
- Set the security properties of the revision of your model. On the Content >
SmartDocs > model page, select Security Settings.
- Check any pre-configured authentication in the model settings page (Content >
SmartDocs) by clicking Settings in the Operations column.
- Update any custom templates to use v6 of the CSS and JS assets, and make changes to reflect any new object names, such as authSchemes and apiSchema. For information on updating SmartDocs templates, see Using SmartDocs to document APIs.
- Re-render and publish your model revision.
- After validating the new documentation, update your production portal to the 15.05.27 release.
If you are an Edge enterprise customer and have questions or concerns about the upgrade process, please email email@example.com and firstname.lastname@example.org. Otherwise, please use the Apigee Community for the best response.
The following bugs are fixed in this release.
|TBD-72||Message logging policy issue|
|MGMT-2124||Permissions of the customer role are reset on saving the permissions in the UI|
|MGMT-2048||User with custom role that limits deployment permissions to one env can deploy in others|
|MGMT-2041||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.
|MGMT-2034||Fetch WSDL returns failure: "Fetch WSDL Error: Error processing WSDL."|
|MGMT-1812||Add TargetEndpoint validation during import
Similar to ProxyEndpoint, the TargetEndpoint will be validated for the proper schema and expressions used in the conditions during the API proxy import.
|MGMT-1345||Import of WSDL with multiple namespaces results in incorrect Build SOAP Step|
|MGMT-800||Creating resource with name 'default' results in broken UI|
|MGMT-602||API Proxy Develop view: Add a Response Cache policy when endpoint does not have PreFlow/PostFlow causes error|
|MGMT-460||Renaming policy results in glitchy behavior, duplicate policy which cannot be removed|
|DEVRT-1565||15-minute intervals for CHARGES|
|AXAPP-1728||Ignore monetization variables in analytics|
|AXAPP-1690||"Invalid API Error" on custom reports|
|AXAPP-1533||Analytics Geomap throws Invalid API Call error|
|APIRT-52||Custom Reports: Response status code for many APIs are null|