Improve template structure using a tree structure and the table for As joints

[ChristianBlei]

Hi,

right now the templates of joints are stored in one table- after some time this table cannot be handled anymore. It would be better to save the templates using a tree structure that the user can define freely. Only the entries of the node selected should be visible in the table. This way the user can create themes and subthemes and subsubthemes etc. and create his own structure of subtypes of a joint type.

BR,

Christian Blei

[haedicu]

Hi Christian,

are you talking about

- connections from connection vault

- customer saved values in the tables of connections from connection vault

- custom connections

?

What do you think, how many "subtheme" levels would be sufficient?

We will be further evaluating this one in the near future and will keep you posted if we need any additional feedback or clarification. Please feel free to continue voting on this one as it will help us with the continued evaluation.

[ChristianBlei]

Hi Udo,

Yes that is what I mainly think of:

The data that is stored in the tables of the connections in the connection vault. Also of cause in the user connections and in the API connections.

I think of a combination of a treeview (oir folder structure) and the table. The table is the content of one lowest level treeview node. How many levels I do not know. I would like to leave that to the user.

In the project explorer for groups and searches As also allows to create folders. I dont think there structure is limited.

BR,

Christian 

[DumitruBerteanu]

Thanks for taking the time to submit your idea and to everyone else for contributing your thoughts and votes. Unfortunately this idea did not get the support of the community over the last 4 months and as such we will not be pursuing it for now. Please feel free to rework and resubmit this one down the road.