vSphere Design Standards

  Your solution integrates into the common tab structure without creating a new, special-purpose tab.
  The Related Objects tab captures the 1-to-many relationship with the open object.
  The Summary tab rolls up key information, as opposed to providing every detail about the object.
  The Summary tab has a Related Objects portlet if the object has a one-to-one relationship with other objects.
  The Monitor tab supports monitoring use cases.
  The Manage tab supports configuration use cases.
  The Monitor and Manage tabs don't duplicate the lists on the Related Objects tab.

  The workspace is read-only.  To enable editing, your solution provides a button that opens the data in a dialog or wizard.

  The Actions menu includes the full set of actions that users can run on an object.
  Your top actions (up to ten) are promoted in the Actions menu.
  You provide a 16 x 16 icon for every promoted action in the Actions menu.
  You use the standard terminology for actions on objects:
New--Creates an object.  "Delete" is the correct opposite.
Add--Creates a relationship between two objects that already exist.  "Remove" is the correct opposite.
Import--Brings information and objects into the vSphere Web Client.  "Export" is the correct opposite.

  The column headings use title-style capitalization.
  The column widths are set to a default size large enough to accommodate the critical data, but no larger.
  The first row is selected by default so that the actions for the objects in the datagrid are displayed.
  Inline editing is only supported if the datagrid appears inside a dialog or a wizard.
  The datagrid supports row filtering, column sorting, and data exporting.
  If the datagrid contains first-class objects (most often in the Related Objects tab), the first column is
the name of the object.
  The datagrid toolbar includes no more than seven actions, with the last place being the Actions menu.
  The toolbar uses icons to represent the actions.
  The toolbar does not include destructive actions.

  The window title uses title-style capitalization and follows the correct format.
  In a multipage dialog, the TOC uses noun phrases and sentence-style capitalization.
  Controls are left-aligned.
  The submit buttons are labeled "OK" and "Cancel."
  The OK button is always enabled.

  The window title uses title-style capitalization and the correct format.
  The title bar includes a Minimize button.
  The TOC is one level (no substeps).
  The first step is titled "Name and location," if applicable.
  The last step is titled "Ready to complete" and summarizes the data that the user entered in the wizard.
  All other steps use standard action names, if they exist, and start with a verb.
  Each page has a title, and the wording matches the wording in the TOC, or expands on it if the TOC entry was compressed to fit the width.
  The page titles are written in bold font and use sentence-style capitalization.
  Controls are left-aligned on each page.
  The Next button is enabled on every page except the "Ready to complete" page.
  The Finish button is enabled as soon as the user can accept all defaults.

  To avoid clutter, no markings appear on required fields.

  Your solution uses a confirmation dialog for batch operations and destructive actions.
  The question is direct (and doesn't start with "Are you sure...?" or "Do you want to...)
  The button labels are "Yes" and "No" or words that represent the action in the dialog.

  Your solution uses the standard action icons (for common actions such as "edit" and "remove").
  Your solution uses the standard message icons (information, success, warning, error, and confirmation).
  Your solution uses the standard status icons (OK, warning, alert, unknown, and info).
  The icons you provided are easily recognizable and memorable.

  Your solution validates user input.
  Text input boxes in wizards and dialogs contain default values when appropriate.

  Button labels use title-style capitalization and are three words or fewer.
  Buttons that open a dialog or wizard in which users input data include an ellipsis at the end of the label.
  Link text matches the text in the Actions menu, if it exists, or else uses sentence-style capitalization.

  The UI text is concise, specific, and conforms to the standards.
  Menu items, button labels, titles, tabs, and datagrid column headers use title-style capitalization.
  All other text controls, including text input boxes, drop-down menus, check boxes, radio buttons, tooltips, and tree views,
use sentence-style capitalization.