Dynamic source for selections = be able to define that the source for a combo or (multi)selection lists.
The field definition will have an ID or rest path to be called to get the list to be displayed. On server side there should be a rest resource that will respond with a generic list of key/value pairs.
Once this is done also the js of capabilities and tasks can be simplified by removing the internal hardcoded repositories combo handling.
Advantages are that specific lists can be done for example to only select proxy repositories/groups/...
We should consider also including some eventual filter beside of type so we do not have to define multiple sources when they return same kind of data just filtered as for example the repositories groups/proxy example.
In case of yum capabilities this will allow selection of "Repository targets" to be included in views concept.
In case of SP plugin this could be used to allow only proxies for Subscribe capability or select the format of File Sink.