When the user navigates to a context (such as a Monitor tab) that has the potential to show dynamic extensions, the client code queries the dynamicUri for filter choices. The plug-in server returns its visibility choices for the dynamic extensions that apply to the user context. The client code caches the dynamic view choices to speed navigation between the views that pertain to the active vSphere object.

The client code caches visibility choices for only those dynamic views that apply to the current object. For example, if the user navigates to a virtual machine's Monitor tab and the plug-in server returns visibility choices for both a view on the Monitor tab and a view on the Configure tab that apply to the current virtual machine, the client code caches choices for both tabs. The client code does not cache visibility choices for dynamic actions.

The visibility choices for the current object generally remain in cache as long as the user navigates only to tabs for that object. The client code empties the cache when the user navigates to a different vSphere object. Then the client builds up the cache for dynamic views that pertain to the new object.

Note: The global refresh button clears the cache and queries the applicable dynamicUri for filter choices.