We were having problems in modifying connections for Information Steward, as only the access details can be modified through the Central Management Console. If the technical architecture of an ongoing project changes, whether a new database will be used for profiling errors, or a new mirror database will be provided as source systems, the connection details can't be simply modified. A new connection has to be created, affecting all of the existing views dependent on the connection. Changing all the views, validation rules, and binding of rules is very time consuming, especially if the trigger was only a change in database connection.
As a workaround, we had to search the appropriate backend table in the repository system, and directly modify the connection path or name. This only works if the user has access to the database of the repository system, and it doesn't seem like a good practice as well.
Is there any better solution to this issue? Will the next version of Information Steward cater for this limitation?
Thanks in advance for your reply!