A way to modify the default behavior of Elements that can be related

As a Solution builder

I want  A way to utilize the "Elements that can be related" functionality for element pickers that takes into consideration the repository structure adopted in most repositories.

So That I can utilize the awesome "Elements that can be related" functionality which is the default behaviour of the element pickers, without having to worry about the users selecting the '#Parent' Element that I need to have for import and repository structure purposes, and which i also see MooD utilizes in its blueprints for Archimate and TOGAF, so it seems fair to assume that this is best practice across the board. 

Benefits Currently, if i want to be sure that the users don't select the #Element i need to either set a query for the contents of the lists for each and every instance of an element picker, or figure out some javascript hack which automatically removes it from the selectlist, both of which i'd rather not do.

Instead it would be preferable to be able to modify the behavior of "elements that i can relate to" to include whichever where clauses i need for the parameter that then generally applies to the repository, which could for instance be: Element name does not contain "#" or "!" or Parent is not of Type, Boolean field is not, etc. 

The intention being to be able to handle not just the exclusion of the parent element, but also the exclusion of possible other elements that exist of that type for Metamodel, test, or other purposes.

In particular it would make it much more feasible to use to "All editable fields for panel subject" functionality of the Inline element form editor, as it's currently not possible to define the contents of the list for relationships included in this way, but using that functionality is a great way to enable generic editing for a large repository.  

Acceptance Criteria 

1. The ability to modify the behavior of Elements that i can relate to for the entire repository, ideally using the existing query editor (perhaps with the features that create a new query block removed), but it could also work as custom SQL. 

Customer / Originator Solution builder

Priority Medium