Mithrilhall,
Those are excellent ideas for improvement.
1) Here are a couple of methods to collapse all on Node List refresh.
Select File->Settings. From the "Node List" panel (top one in the list) select the expansion level from the "Automatically expand the Node List to the XXXXX level" drop down. If you set this to Group, the Node List will be collapsed after a refresh.
Another method is to hold down the Control key and click on any '+' or '-' at the Group level in the Node List. This will Collapse/Expand everything at that level. But... I do not reccomend this approach for expanding all Nodes and showing Configs. Expand to all Configs does not work, you should expand them one at a time.
2)You are correct, the column sorting within the Import Wizard no longer functions. We'll look into it.
3)Hiding all duplicate Nodes is a good idea. Thanks !
4)Alphabetize the password drop downs works... kind-of. If the passwords in the databases are NOT excrypted, the passwords are sorted alphabetically. If they are encrypted, the encrypted version is sorted alphabetically, then they are decrypted and displayed. Oops, we goofed here. That little bug sqeaked through testing. Thanks for letting us know.
5)Turning off the auto-complete for passwords is not possible at this time.
6)There are a couple ways to "keep the newest xx configs". One method is to simply display only the last xx configs in the Node List. Select File->Settings. There is a slider on the "Node List" panel that allows from 1 to 100, or all configs to be displayed when the Node List is expanded. For example... if you set the slider to 10 configs. The last 10 configs will be displayed in the Node List when expanded. When you right-click on the Node and select "Edit Selected Node". All the Configs are available on the "Configuration History" tab. So... this change affects the number of Configs displayed, all Config are still kept in the database. (by the way... there is a release of Configuration Management where this does not function correctly, Setting the scroll bar to anything less that "All Configs" will cause the Node List to display "Loading Configs ..." or nothing)
A second method is to "Purge Old Configs". Select Configs->Purge Old Configs. From this dialog, you can delete all Configs from the database except the last XX. In a future release, "Purge Configs" will be available as an Scheduled Job. We purposely disabled the "Purge Old Configs" Scheduled Job in the current release.
One more item about "Keep the last xx Configs".....
A "Only Download Changes" option will be added to the Config Download process that will compare the download to the last config in the database. If there are no changes, the downloaded Config will not be added to the database. This would allow you to only store Configs that have changed in the database.