The Integrity Modeler 9 shows old Enabler directory from deinstalled version 8.5. But it doesn't work anymore. There should be a way inside the Integrity Modeler to remove Enabler databases from Integrity Modeler 9 which works with SQL databases.
The topic above is not only valid for old Enabler databases. There should be a "remove" option in general.
Additionally invalid entries are also simply created if a new server is added with the default name, for whatever reason.
And last but not least there should be an option to show local databases per default (just like for the old enabler database). It takes unnecessary effort to explain to every user how to add the server instance itself, especially if the server and sql instance is transparent for the user otherwise.
The "right-click" seems to me like a user unfriendly work-around and none of my users is comfortable with it.
There is a general problem with "right-click", it doesn't work from user perspective if the repository or instance doesn't exists (Enabler or SQL or wrong entered instance name). If you right-click then nothing happens visually and it may take 15-30 minutes before the context menu shows up. Additionally, it happens then only if you have not clicked anything else within this time. You cannot expect that users know that they have to wait such a long time for a context menu doing nothing else in between and that they actually do it willingly. In the special case of old Enabler repositories the application should detect that they are not SQL databases and remove them automatically. Even for not existing/accessible SQL instances/databases a faster solution is necessary.
A similar problem exists for the "last opened" which is automatically selected if the Model Explorer is opened. But also here the "last opened" is totally counterintuitive because it never shows really the "last opened" but from user perspective some random model that was opened in the past. Here the application should also detect automatically if it exists and if not then remove this entry (from registry), because this "last opened" model entry also keeps repository entries alive that are not bookmarked anymore.
And as a note, you should also not expect the user to work locally with admin rights. Most often the users will not have access to the registry themselves. So they also cannot change the Model Explorer entries there.
This is the most reliable approach we have but I agree it is not the most user friendly. Thanks for your input and we will look to improve in the future.
regards,
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
