I agree we aren't being inconsistent here, but let me ask you... which methodology do you prefer?:
- Select the type of entity, and then see the configuration options for that type (this is the way the External Configuration page works today)
- Have a default entity selected, allow the user to change the type of entity, and then have the configurations options switch from one type to the other (this is the way the Data Collector page works today)
I prefer option two, the Data Collector workflow. It's cleaner. You have a list of configurations on the main page and then you click a button to perform an action on one or more of the items. All configuration choices are made on the edit/update page. You bring up that page with a default object type selected that the user can easily change.
By the way, I also think the object names in the list should be links. If you want to view the details of a Data Collector or an External Configuration, you should not have to check a box and then click a button. This is a web interface. The name of the Data Collector or External Configuration should be clickable links. Clicking on the name should take you to a view-only mode of the details. Once there, you should have the option to go into Edit mode.