The ability to duplicate components would give a better starting point for components that need to be configured similarly. For example, I like components that collect little data and do so infrequently to have no data filter and have the logging level set to "Trace". For the AVEVA Adapter For RDBMS, it would be nice to have 2 identical components other than their names and their data collection mode. I could like one to use "CurrentWithBackfill" and the other to use "HistoryOnly" so that I can perform history recovery without interrupting the flow of real-time data. When a component is duplicated, allow the user to enter a new name (component ID) for the duplicate.
Since duplicate components would mean that 2 components would now be trying to get data instead of just 1, duplicated components should be disabled by default, which means that we need a setting to enable or disable components. This setting would be useful even outside of component duplication. This would allow you to disable a component until you are done configuring it without having to stop the AVEVA Adapter entirely and disrupt the data flow of other components and without having to use odd workarounds like purposely misspelling the data source until the component is ready.
Lastly, the duplication of components would give us an indirect way to rename components. While this is not as straightforward as direct renaming (which I would encourage AVEVA to consider), and it would still result in a new set of logs being created for the new component, this method of renaming a component is still easier than attempting to do the same thing without the AVEVA Adapter Configuration Utility.
