vSphere Web Client SDK 6.5 Update 2 Release Notes

vSphere Web Client SDK 6.5 Update 2 | 03 MAY 2018 | Build 8307201

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of the vSphere Client SDK introduces the following new features:

  • JavaScript API - The vSphere Client SDK has a new JavaScript API that provides a simplified interface to manage user interface elements of your plug-in.
  • HTML5 sample - The vSphere Client SDK contains a new HTML 5 sample, which shows how to use the new JavaScript API.

Deprecated Features

None

 

Earlier Releases of the vSphere Web Client SDK

Known Issues

The known issues are grouped as follows.

vSphere Client SDK
  • Missing Virgo log files on Japanese OS installations.

    The log files of the Virgo server are missing on Japanese OS installations.

    Workaround: To resolve this issue, you can try the following:

    1. Open the vSphereWebClient\configuration\serviceability.xml file with a Hex editor.

    2. Remove the first three invisible bytes (EF BB BF) and save the file.

    3. Restart the service of the vSphere Client.

  • The WEB_PLATFORM.setDialogSize() API is not supported in the vSphere Client

    You can use the WEB_PLATFORM.setDialogSize() function to change the size of the dialog box at runtime when developing HTML-based plug-ins for the vSphere Web Client. This function is not supported for developing HTML plug-ins for the vSphere Client 6.5.

    For developing HTML plug-ins for the vSphere Client, you can set the size of the dialog box upon opening the dialog.

  • String resources are not reloaded when you use the pickup directory to deploy your HTML plug-ins.

    The WAR bundle of an HTML plug-in contains localized string resources that are visible in the UI. In a development environment, if you use the pickup directory of your local vSphere Client to deploy and test your HTML plug-ins, you must first deploy the WAR bundles of your plug-in package. When you update the WAR bundles, the Virgo server does not reload automatically the localized string resources.

    You must restart the vSphere Client Virgo server after updating the WAR bundles in the plugin-packages folder.

  • The ${namespace}.manage.tagsViews extension point is not supported in vSphere 6.5.

    In the vSphere Client 6.5, you cannot add a view under the Tags second-level tab of the Configure tab by using the ${namespace}.manage.tagsViews extension point. You can find the Tags second-level tab under the Tags & Custom Attributes application in the vSphere Navigator.

    None. If you have existing HTML-based plug-ins that use the ${namespace}.manage.tagsViews extension point to add views under the Tags second-level tab, you must change their implementation to use another extension point.

  • Chassis object property updates do not show.

    The vSphere Client does not show updates to a Chassis object until you refresh the view. When you select Edit Chassis and modify properties, then click Update Chassis, the object updates in memory but the changes do not show immediately.

    Click the Global Refresh button, and the view updates the properties on the screen.

  • 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.

    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>
vSphere Web Client SDK
  • Google Chrome problem with WEB_PLATFORM.

    Several method calls in the WEB_PLATFORM container app in the Flex-based client work the first time an HTML plug-in opens, but fail on subsequent calls. Calls that fail include WEB_PLATFORM.getObjectId(), WEB_PLATFORM.getActionUid(), and others. This problem happens with HTML plug-ins running on the Flex-based vSphere Client on Google Chrome (version 55.0.2883.87 and later).

    To resolve this issue, update the file web-platform.js with the following code and rebuild your plug-in:

        var WEB_PLATFORM = self.parent.WEB_PLATFORM;
        var isChromeBrowser = (window.navigator.userAgent.indexOf("Chrome/") >= 0);
        var isFlexClient = !!self.parent.document.getElementById("container_app");
        if (!WEB_PLATFORM || (isChromeBrowser && isFlexClient)) {
          WEB_PLATFORM = self.parent.document.getElementById("container_app");
          if (isChromeBrowser) {
            // Object.create is required to support Chrome version >= 55 on Flex client
            WEB_PLATFORM = Object.create(WEB_PLATFORM);
          }
          self.parent.WEB_PLATFORM = WEB_PLATFORM;
                     
  • Missing Virgo log files on Japanese OS installations.

    The log files of the Virgo server are missing on Japanese OS installations.

    To resolve this issue, you can try the following:

    1. Open the vSphereWebClient\configuration\serviceability.xml file with a Hex editor.
    2. Remove the first three invisible bytes (EF BB BF) and save the file.
    3. Restart the vSphere Web Client Service.
  • The ${namespace}.manage.tagsViews extension point is not supported in vSphere 6.5.

    In the vSphere Web Client 6.5, you cannot add a view under the Tags second-level tab of the Configure tab by using the ${namespace}.manage.tagsViews extension point. You can find the Tags second-level tab under the Tags & Custom Attributes application in the vSphere Navigator.

    None. If you have existing plug-ins for the vSphere Web Client that use the ${namespace}.manage.tagsViews extension point to add views under the Tags second-level tab, you must change their implementation to use another extension point.

  • When a menu or a dialog overlaps an HTML view, the view becomes blank.

    Log in to the vSphere Web Client by using Mozilla Firefox version 31.0 or earlier. When you open a menu or a dialog which overlaps an HTML view, the view is hidden temporary and is displayed as a blank pane. This issue has no functional impact and the view is restored once you close the menu or dialog.

    Use another supported browser or a more recent version of Mozilla Firefox.

  • Global refresh error with plug-in portlet.

    The Global Refresh button causes internal error #1009 if the user clicks the button upon first entry to a view containing a plug-in portlet. This problem is caused by a limitation in the SDK.

    Navigate to another view with a plug-in portlet, then back to the original view, before clicking the Global Refresh button.

  • Chassis object property updates do not show.

    The vSphere Web Client does not show updates to a Chassis object until you refresh the view. When you select Edit Chassis and modify properties, then click Update Chassis, the object updates in memory but the changes do not show immediately.

    Click the Global Refresh button, and the view updates the properties on the screen.