You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Wednesday, March 4, we will begin releasing a new version of the Apigee Edge integrated portal.
New features and enhancements
This section describes the new features and enhancements in this release.
Enhancements to audience visibility management
Enhancements to audience visibility management have been implemented in this release. For more information, see:
- Manage the visibilty of an API in your portal (Beta)
- Manage the visibilty of a page in your portal (Beta)
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|
Logos for original version of portal cannot be updated
An issue has been fixed that was preventing the logo from being updated in the original version of the portal.
Background image placement
The portal background image is now centered by default to better accommodate varying screen sizes.
APIs are no longer showing images after uploading a new asset
An issue has been fixed that was removing the images associated with APIs from the APIs page when you uploaded a new asset.
Menus items cannot be edited
An issue has been fixed that was preventing menu items from being edited.
Menus Header/Footer drop-down is obscured under sidebar
A layout issue has been fixed that was causing the Header/Footer drop-down menu on the Menus page to be obscured by the sidebar.
My Apps page is showing a developer's applications from multiple organizations
A caching problem has been fixed that could cause a developer to see their applications from multiple organizations on their My Apps page.
Positioning of the tiles on the portal landing page changes while loading
The positioning of the tiles on the portal landing page no longer changes as the page is loading.
Allowlist does not affect existing accounts
The section Restrict portal registration by email address or domain describes how to you restrict portal registration by identifying the individual email addresses or domains that can create accounts on your portal.
The following note has been added to this section for clarification:
For a list of known issues with the integrated portal, see Known issues with the integrated portal.