You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Wednesday, June 15, 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.
Expiry/refresh default in Key Value Map Operations policy
They Key Value Map Operations policy lets you determine how long values are persisted before
being refreshed. The refresh interval is set with the
element. If a GET operation is executed and the expiry interval has been exceeded, the value is
refreshed and the policy gets the updated value. When you add this policy to an API proxy, the
default expiry time is now 300 seconds. (The previous default was -1, which means values are
never refreshed.) (EDGEUI-579)
The following bugs are fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.
|EDGEUI-566||Blank page after logging into management UI|
|EDGEUI-564||Users receive permissions errors on management UI login, then they're automatically logged out|
|EDGEUI-549||Error showing data on the API Proxy Performance view|
|EDGEUI-544||Custom Roles page displays incorrect value for Delete Reports permission|
|EDGEUI-504||Confusing status on Developer Apps, Keys, and Products|
|EDGEUI-120||Internal Error page email link has an invalid email address|
|DEVRT-2301||Monetization: UI alignment with API on published rate plans
With regard to the expiration date on published rate plans, the management UI now matches the behavior of the management API. If a rate plan has an End Date specified, you cannot change its expiration date. For more information, see Expire a published rate plan.
This release has the following known issues.
|EDGEUI-545||Business Transactions dashboard and proxy performance reports
If you have configured API proxies with URI patterns, then the Business Transactions dashboard and proxy performance reports may return an error for those API proxies. This issue will be resolved within 8 weeks, and these queries will begin functioning as expected. This will not impact you if none of your API proxies are configured with URI patterns. For more information, see https://community.apigee.com/articles/23936/alternative-to-business-transactions-api.html.