The left-hand tree of the Configure tab page adds an extension point that contains submenus.

[dhbtemp]

Hi,

I have an idea, I would like to configure the label on the left side of the page tree to add an extension point that similars to the system and its submenus. As shown in Fig.

After I click the system option, the system options sub-options are displayed, then you can click on the demand to display the contents of the sub-options.

If I could also add an extension point that contained sub-options, it would save space in the content area and make our plug-in content look better.

About this idea,I do not know the current expansion point configuration can be done, if so please tell me the method, thank you.

[irahov]

Hi, dhbtemp,

Could you please add a screenshot which includes the whole window and be in English.

I suppose you refer to the main workspace area where there is a tree-like structure for the 'Monitor' & 'Confiure' tabs content and not the one described in this post: https://developercenter.vmware.com/forums/4974/vsphere-web-client-sdk#541964|3497823

[dhbtemp]

Hi,rahov,

Figure, this is what we want to make the expansion point of the general look.

[dhbtemp]

Hi,irahov,

Html client does't support Administrator menu right now?We want to support Role and privileges down Administrator.

[irahov]

At my first convenience I'll take a look and give you an update on the content-tree capabilities of the Configure tab and what is supported by the SDK

[irahov]

With regards to the Administration, yes it is still not available out of the box but it is a work-in-progress.

For additional information you may take a look at this comment 6 of the 'Fling 4 Multiple Resources and Administration' forum post - Re: Fling 4 Multiple Resources and Administration

[irahov]

I've just now verified that currently there is no capability exposed to develop a tree-like structure in the configure tab.

On the other side you can use a number of "vsphere.core.${objectType}.manageViews" extension points (or  ${namespace}.manageViews in case of your own custom object type)

that will give the same functionality, i.e. you can build the 'branches of the tree' without the grouping capability (the root).

[laurentsd]

FYI, the reason the "Table of Content" list on the left of Manage and Configure views is only 1 level deep is for UX consistency.  We don't want plug-ins to inject an arbitrary complex structure when extending Configure and Manage.   If you have a lot of information to display you should organize it as best as possible within a single view and not with a long list of separate Configure or Manage entries in the left hand side.   You are free to use a tree structure within your own view if it is the UX that works best for you.