I am trying to understand the behavior of the solutionMenus extension point in vSphere web client 5.5 and 6.0.
I have experimented using the vmactions_ui (..\flex-samples\actions\vmaction-ui) project which is part of the sample provided by the SDK 6.0.
Note: Our plugin is compiled with the 5.5.2 SDK.
When the property condition in the metadata filter defined in the solutionMenus is false, a default “flat” menu ("All <plugin name> Actions") is seen for 6.0 but no menu is shown in the 5.5 web client. There seems to be an inconsistency in the behavior. Is there any work around to prevent the default “flat” menu coming up in 6.0? Is the behavior considered a bug?
A plugin.xml is attached that can reproduce the above issue when used in the vmactions_ui project. The plugin.xml contains a <metadata> filter on the solutionMenus extension point which filters on both object type and property conditions.
Steps to reproduce the behavior:
1. Login to vSphere web client and select VMs and Templates
2. Right click on a VM to view the Actions menu
Observe:
In the web client 5.5
If propertyCondition is not satisfied -> UI does not show any options at all. The menu item is removed.
In the web client 6.0
If propertyCondition is not satisfied -> UI shows "All <plugin name> Actions" and in the sub menu "No options available".
Thanks,
-Darrell