times

vSphere Client SDK 7.0 Update 1 | 6 OCTOBER 2020 | Build 16846352

Check for additions and updates to these release notes.

Overview

The vSphere Client 7.0 U1 SDK enables development of vSphere Client plugins supported on both vSphere and VMware Cloud on AWS.

What's New

This release of the vSphere Client and the SDK introduces the following plugin features:

Dynamic extensions: Control visibility of Monitor views, Configure views and Menu actions based on plugin-defined conditions.
Support for plugin actions on multiple target objects of the same object type (acceptsMultipleTargets property).
Plugin multi-manifest contains the prioritized list of separate plugin manifests per feature set. This enables support of multiple vSphere versions with the same remote plugin.
Ability of a remote plugin to indicate the vSphere Client versions it can be deployed on and the vCenter Server versions it supports (vsphere.client and vcenter.server properties).

All new features have been demonstrated in the SDK remote plugin sample which has also been upgraded to:

leverage new library versions (Clarity Design System 3.0 and Angular 9).
declare custom privileges and tasks.
detect plugin data changes and refresh plugin views via WebSocket.

Resolved Issues

vCenter Server registration script for setting up development environment sporadically fails

On rare occasions the server-registration(.sh/.bat) script is unable to copy the development setup files to the folders expected by the local vSphere Client instance.

Fix: The vCenter Server registation script copies all necessary setup files.

Plugin Cards are missing from the secondary VM Summary page design

The new VM Summary page design is a card container-based layout which is Off by default. It can be switched on by the user but does not support plugin cards yet.

Fix: Plugin cards are shown when switching to the new VM Summary page layout.

Known Issues

Two portlets in the same plug-in cannot share the same URL.

When a vSphere Client plug-in contains two portlets, they must specify different values for their attributes. Otherwise, a global refresh operation updates only one of the portlets.

Symptoms: Global refresh updates only one of the extensions having the same URL.

Workaround: Assign different URLs to the two portlets. For example:

   <extension id="portlet1">
          ...
                  <url>/vsphere-client/chassisa/resources/host-portlet1.html</url>
          ...
   </extension>
   <extension id="portlet2">
          ...
                  <url>/vsphere-client/chassisa/resources/host-portlet2.html</url>
          ...
   </extension>

Memory leak with Microsoft Internet Explorer 11.

vSphere Client's memory consumption increases steadily when using Microsoft Internet Explorer 11 with iframes in vSphere Client plug-ins. This is a known general issue with iframes on Internet Explorer.

Symptoms: Memory increases on IE11 with each opened plugin iframe leading to OutOfMemory error after some time.

Workaround: Use other browsers supported with the vSphere Client, such as Chrome or Firefox. List of supported browsers includes Microsoft Edge version 38 and later, Google Chrome version 50 and later, and Mozilla Firefox version 45 and later.