Home > Forum > User Voice > Improvements for advanced configuration of picker fields and data sources

Improvements for advanced configuration of picker fields and data sources
0

Hi,

right now there is no possibility to configure a template in a data source that could be used when selecting this data source in a picker field for the advanced configuration. Each time the advanced configuration has to be set up manually. Pickers for users or departments are used very often and it's a mess to reconfigure each time the wished default advanced configuration - especially for the columns configuration in the "General" tab. As a workaround we have created a "Template App" with a template process containing those commonly used form fields. If we need one of them we create a relation to this template process from the edited process and do a copy paste of the form field. But this still has no inheritance that we would like related to a default advanced configuration template

Suggested improvements:
- Add a button "Advanced configuration template" next to test button in the data source configuration. Here there should be all possibilities to set default preferences for the choice types dropdown, picker/pop-up and autocomplete
- Add a button "Load template" next to the "Advanced configuration" that automatically sets all config from the template. The best way would be a relationship to the template with the option of breaking it's inheritance
- Add a button"Read template" next to "Read" button in "General" tab of the advanced configuration under the columns configuration. A click should automatically set all columns as they are configured in the data source template. This is a special case to only load the columns configuration instead of the whole configuration

In the case of switching the data source of a picker field (e.g. a department picker with MSSQL data source shall be replaced by a new REST Web Service data source) such a template would significantly simplify the migration.

Not so nice but better than now:
- Add an option to export an advanced configuration (XML or some kind of) and an option to import an advanced configuration with a small check if the data source of export is matching the one of import to avoid missmatch

What do you think about these suggestions?

Kind regards
Sébastien

Nobody has replied in this thread yet.