Evaluate your plug-in's integration within the vSphere Client UI using the criteria listed here. Although this checklist can help you get closer to certification , you need not use every item in your design.
Navigation A link to your plug-in's main view is on the Shortcuts page .
A link to your plug-in's main view is in the top-level of the Navigator .
Links to your global views are in your plug-in's level of the Navigator (and not the top-level).
Links to your object inventory are in your plug-in's level of the Navigator (and not the Global Inventory).
If your plug-in has a global view for configuring settings, your link to this view appears in the Administration level of the Navigator .
Link text is clear, concise, and conveys the identity of your plug-in.
Object Workspace Your plug-in integrates object data into the Summary, Monitor, and Configure tabs.
Your data on the Summary tab rolls up key information, as opposed to providing every detail about the object.
Your monitoring use cases (day-to-day activities) are highlighted in views on the Monitor tab .
The settings for your objects are organized into views in the Configure tab .
The object workspace is read-only. To create an object or enable editing, your plug-in opens the data in a modal .
Actions Your actions use the standard vSphere Client terminology .
If an action has an icon, it easy to recognize and remember. Not every action requires an icon.
Modals Your modals follow the Clarity design guidelines for modals .
For large modals , the backdrop covers the entire vSphere Client. For smaller modals, the backdrop can be local to the workspace area.
Wizards Your wizards follow the Clarity design guidelines for wizards .
For 4 or more steps, the last step reviews the user-entered data.
Components and Styling Your plug-in follows the component styling and usage guidelines of the Clarity Design System .
Text UI text is concise and specific.
Labels don't use colons.
