You're viewing Apigee Edge documentation.
View Apigee X documentation.
On Thursday, January 7, we will begin releasing a new version of the Apigee integrated portal.
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.
|Issue ID||Component Name||Description|
Unable to link to API category from navigation menu
You can now link to an API category from a navigation menu using its full or relative URL.
API requests slow to respond, sometimes return
An issue has been fixed that was causing API requests to be slow to respond.
Improve security of
Update configuration to use
API details page: Audience display issues
Minor formatting improvements have been implemented in the Audience section on the API details page. Specifically:
Developer emails should not be case-sensitive for members of developer teams
Developer emails are no longer case-sensitive for members of developer teams.
Organization administrator not able to view developer account information with error "Visibility of PII is restricted by role"
An issue has been fixed that was preventing organization administrators from viewing developer account information.
Nested menu item with no parent breaks portal
Previously, you could publish a header or footer menu that contained a nested item without a parent, but it would prevent the portal from rendering. Now an error is thrown if you attempt to publish a menu with a nested item that does not have a parent.
Changing a portal page URL breaks any assigned audience permissions
Previously, if a page path was modified, then all its associated permissions were lost and the page was invisible to everyone. Now when a page path is modified the associated permissions are maintained.
For a list of known issues with the integrated portal, see Known issues with the integrated portal.